On 24 January 2011 01:53, Julien Nicoulaud julien.nicoulaud@gmail.com wrote:
Thanks for the infos and script Dimitar !
2011/1/23 Dimitar Zhekov dimitar.zhekov@gmail.com
On Sun, 23 Jan 2011 13:07:31 +1100 Lex Trotman elextr@gmail.com wrote:
a. who owns the preferences? preventing multiple instances from changing preferences is very limiting, if they can all change them, who saves their set when Geany terminates? and how to lock them irrespective of the filesystem they reside on to prevent scrambled preferences?
Why not save preferences right when closing the preferences dialog ? That's what I would except as a lambda user.
Hi,
Unfortunately the "preferences" includes things that are not set in the prefs dialog, eg screen layout recent files etc. Writing this stuff whenever it changes would mean constantly writing the prefs file and in the absence of locking (which is not available for all file systems) would increase the chances that two instances would try to write it at the same time.
And then there is project session stuff, again writing it all the time is risky, writing it at the end is a who wins problem.
Cheers Lex
PS The prefs file currently also includes some session stuff but I'm assuming that gets moved when session support is added, but the project session stuff can't be
Windows: the instances are stopped one by one. The last one wins. X11: the session management supports instances.
b. how do you restart multiple instances? which leads to session management being required, but Geany has two potential implementations of that and no clear path forward yet
It has a complete sm for the current single-instance behaviour, and an incomplete multi-instance sm for the non-implemented multi-instance behaviour. So the real question is, do we plan to introduce any multi instancing in Geany in the foreseeable future? If not, the last single-instance sm applies against 5530, and is quite stable.
c. the same issues relating to preferences apply to project files being used by more than one instance, or if a project can be open in only one instance how to enforce that?
The same answer as for a. and b.
d. and of course these also apply to the same document file being open in multiple instances, at logout/shutdown who's copy gets saved? how do you detect the fact so you can at least warn the user? remember that locking and the like don't work on remote filesystems.
Both Windows and X11-sm will ask you for any modified files.
(In the current implementation, both simply terminate.)
-- E-gards: Jimmy _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany