On Sat, 27 Feb 2010 09:05:12 +1100 Lex Trotman elextr@gmail.com wrote:
To be easy to implement, perhaps maybe only the first/main instance should save settings. We could have a Tools->Save Config menu item enabled for the first instance to allow the user to restart other instances with the new settings.
I havn't looked in detail at what the -i option does but I assume it doesn't use or accept socket connections.
Yes. The socket code only works for the 'main' instance.
If so then I assume all Geany commands without the -i will be the same instance, and this is the one that should be able to save.
(If a second instance of geany is run without passing filenames to the first, -i is implied).
There needs to be a visual distinction of instances that can & can't save.
I agree, otherwise the user might think there was a bug saving settings.
I wouldn't worry about the other -i instances being able to get settings until the main closes.
This was just an extra feature I personally would find useful (force saving settings without quitting). Otherwise you would have to quit just to 'update' settings for new instances to read.
Also, force saving settings can be useful when developing (e.g. running recent trunk code for real work, as I do to help test it). So I don't lose e.g. paragraphs in Scribble due to a segfault.
Regards, Nick