[Geany-devel] Race condition when saving geany.conf

Dimitar Zhekov hamster at xxxxx
Tue Mar 2 17:25:50 UTC 2010


On Tue, 2 Mar 2010 16:02:48 +0300
Eugene Arshinov <earshinov at gmail.com> wrote:

> I'm not sure I understand you message correctly, but the problem I
> described is about saving the global Geany settings, not about the way
> how to pass instances' settings "across restarts".

In short, save <smclientid>.conf files instead of "geany.conf". That
will not save any global options, so if you restart the session
and then launch a new geany, it will not use such saved options.
However, if you launch a geany instance _without_ restarting the
session, exactly the same thing will happen. The question seems, then,
is save session considered to be "quit and save my settings for
future use", or "next time, restore the things exactly as they were".

> [...]

> [An example insignificant problem] If you change something in an
> instance run with "-i" and restart, you'll loose your changes as they
> won't be saved anywhere.

Another insignificant problem is that if the same project is open in
two or more instances, that may cause a project file race.

More important than that, however, the --config option (if any) passed
to geany should be replicated in the session arguments. First, the
geany socket is in the configuration directory, which means one primary
instance per directory. Second, if you restart the instances without
--config, they will all grab the default geany.conf, forgetting
their's saved <directory>/geany.conf files.

--
E-gards: Jimmy



More information about the Devel mailing list