On Wed, 10 Oct 2012 10:07:19 +1100 Lex Trotman elextr@gmail.com wrote:
On 10 October 2012 06:58, Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
a project-less build -> set build commands -> ok saves the changes under filedefs/ immediately ("save filetypes now" in the mailing list). Just fill some commands, OK, and grep ~/.config/geany.
It doesn't save the config file though, so no non-filetype settings saved.
Yes. Curiosly enough, these are "ui prefs"...
Save on Quit is needed for the interface preferences, such as View -> Show Sidebar, and the project-less file list. Unfortunately, the file list is saved even with a project open, but attempts to fix it trigger a "multiply instances" discussion.
Yes, Geany does *not* do multiple instances properly, therefore being ignored for now. If you do multiple instances with the same project or config file it will break (ie not do what you wanted), its just a matter of when.
But not saving the file list in geany.conf, if we have a project open and so the list is already saved in $project.geany, is _not_ actually related to multiply instances. Maybe I should propose it again, it's a very simple change.
The ones from save_ui_prefs(). You can't reasonably expect a file save each time the side bar is shown/hidden, or the main window is moved/sized...
- why not?
Why not save the document in a temporary file on each SCN_MODIFIED? You will never lose a single edit action, and surely a current document content is no less important than, say, the sidebar state. :)
- which is why they should be in the session file not the prefs file,
also, to me, if I arranged windows to fit what I was looking at, it would be good it that was restored with the project session as well.
Definitely, from using xsm, I know very well how convinient per-project interface is. But it doesn't really require a session file - we can store the ui_prefs in our current project file, which is saved on project close and geany quit.
(Now that I think of it, multiply sessions per project do not require a session file either.)
Splitting has it's own merits, of course, and if implemented, the ui prefs should logically go in the session file.