At times, I'm working on a project with a large number of files open. As the project has special needs for building and running, I've configure the project's Build properties accordingly.
Now, regularly I have do a quick edit in another program, and run it, but can't because it has other 'Build' requirements.
This presents a hazardous situation: If I close all files (to run the single one), I automatically clear the project file of the large project I'm working on. So I need to first close the project, then re-open the single file.
I see the following solutions: either
- Allow geany to work on several projects simultaneously (would be great) - When 'Close'ing all files if a project is active (or even when closing just one file), WARN the user that this will modify the project's file list too - When a new file is opened, ask if it is to be included into the project, else use the default Build Commands.
The above scenarios happened to me 3 times over 2 days. Of course this could be an indication I'm getting to old to do this...
John
This has happened to me in past to... But I've soon learned to simply do the quick edit in another instance of Geany. It is definitely easier than closing project, doing the edit and reopening the project.
In my experience, working with projects in Geany is confusing enough as it is. Supporting multiple open projects would only make it worse. And adding warning or "add to project" dialogues would be pretty annoying.
If you need different build commands why not just add more to the menu?
See https://www.geany.org/manual/current/index.html#id131 `Build menu` section and my PHD thesis https://wiki.geany.org/howtos/configurebuildmenu.
Allow geany to work on several projects simultaneously (would be great)
Remember a Geany "project" is just a named session file plus a few settings. So "working on several projects simultaneously" does not fit with its basic concept. Its for restoring where you were at when you closed Geany, rather than "Project" as Vs or Eclipse etc know it.
When 'Close'ing all files if a project is active (or even when closing just one file), WARN the user that this will modify the project's file list too
We have enough annoying warnings as it is.
When a new file is opened, ask if it is to be included into the project, else use the default Build Commands.
Originally the session file list was only saved at close given its original concept, its "fairly recent"[^1] that it was saved on any change of files or settings.
More complex project behaviour is of course possible, but as @dolik-rce says, the interaction is annoying enough as it is (incidentally see #3042, maybe that will help). More complex project handling is something plugins might be better off handling since everybody has a different idea how it should work.
[^1]: "fairly recent" in Geany terms
github-comments@lists.geany.org