On Tue, 2 Mar 2010 15:23:31 +0300% Eugene Arshinov <[email protected]> wrote:
> On Mon, 1 Mar 2010 16:08:18 +0000% > Nick Treleaven <[email protected]> wrote: > > > On Sat, 27 Feb 2010 09:05:12 +1100 > > Lex Trotman <[email protected]> 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). > > > > I really like this idea. It is simple to understand, rather > convenient and uniform with the behaviour of "new-instances", i.e., > those instances should not touch any global data, either the default > session or the settings. > Now committed, together with "Tools > Save configuration" menu item. Though, I think we should think of a better name for it as currently "Save configuration" and "Reload configuration" mean different things by configuration, which will probably confuse users. > > > 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. > > > > Any proposal for this visual distinction? > > Best regards, > Eugene. _______________________________________________ Geany-devel mailing list [email protected] http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
