@kugel- agree its useful (see https://github.com/geany/geany/issues/1763#issuecomment-364107685) but its not backward compatible, an old geany would not find the session file, we often get situations where users have differing versions of Geany that are sharing files (two machines with different distros for eg). So a setting is needed (despite how common it is, me saying "needs a setting" isn't automatic, I do actually think about it :-).
> What's missing is the same treatment for projects. I think open project files > can also be saved in session.conf, with the project name as the key (or some > other unique identifier). The project files can then be checked into VCS, and > the corresponding "open project files" list does not clutter the checkouts. Its necessary to have the whole config directory inside the VCS tree, not just `geany.conf`, because its only possible to specify the whole config (with -c) not `geany.conf` by itself, and that then lets the OP change and share _all_ settings including keybindings and those in filetypes and geany.css and tags for libraries they use etc, on a per repo (ie per project) basis, and they then have no need for Geany projects which have only a few settings and the session so its outside this use-case. But it raises the point that the open project is saved to `geany.conf` that probably needs to move into the session too. If they did want to change projects even if its outside their use-case there doesn't seem any reason not to split into `project_name.geany` and `project_name.geany.session` next to each other in the same directory, `.gitignore` could be taught to ignore it and it works for projects stored outside the tree too. Not sure if that would break the project plugins though? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2776#issuecomment-813125040
