I'm not sure if XDG_CACHCE_DIR is appropriate. Normally it contains files that can be regenerated by programs without user interaction...

• Same folder as project file – This feels like clutter to me. Why split project files if they're going to be kept together anyway? But depending on what settings are considered "session", it could make sense.
• Don't split project file into config/session. If projects are migrated to the stash system, depending on how stash is extended, not splitting project files could be configured as an option.
• Add another paths option. Chicken-or-egg problem, for people who consider paths to be "session" settings.
• ~/.cache/geany/sessions/ – I suggested this location because the types of settings I'd expect to be categorized as "session" are what Geany manages on its own. There's little consequence if MRU, geometry, position, etc are wiped out. There's some inconvenience if currently open files are lost, but they can be reopened. The cache directory is also long-lived, so session settings wouldn't normally be lost.
• ~/.config/geany/sessions/ – This location may be difficult to find to remove left-over session files when project files are renamed or deleted. It wouldn't matter if Geany removes session files for project files that no longer exist.
• /tmp – This location is potentially wiped out at every boot. "Sessions" should probably be able to persist across reboots.

As to stash, the suggestion would be that stash supports overriding where sources of a specific setting override another. See for example how the build menu overriding works.

#3000 (will be split into ~6 PRs) includes an override for non-GUI settings in stash. I wrote it with plugin use in mind, but it (or something similar) could also be used for projects, sessions, etc.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.