[Geany] Per-workspace instance of Geany

[Lex Trotman]

2011/1/26 Krzysztof Żelechowski <giecrilj at stegny.2a.pl>:
> Dnia środa, 26 stycznia 2011 o 00:57:48 Lex Trotman napisał(a):
>> 2011/1/26 Krzysztof Żelechowski <giecrilj at stegny.2a.pl>:
>> > Dnia wtorek, 25 stycznia 2011 o 14:27:18 Randy Kramer napisał(a):
>> >> On Tuesday 25 January 2011 04:04:53 am Krzysztof Żelechowski wrote:
>> >> > Dnia wtorek, 25 stycznia 2011 o 00:43:11 Lex Trotman napisał(a):
>> >> > > Your description of single instance, multi window is correct, yes
>> >> > > there is a slightly enhanced risk, but IMH(unbiased)O compared to
>> >> > > the problems with multiple instances this is small, see my scenario
>> >> > > on another post on this thread.  No software can prevent the same
>> >> > > file in two instances being different.  With a single instance all
>> >> > > windows see the same (possibly modified) version of the file.
>> >> >
>> >> > Open Office, for example, can: all other instances are either
>> >> > detached (as in stationery) or read-only.
>> >>
>> >> Krzysztof,
>> >>
>> >> Is that on Windows or Linux?  (I can imagine differences between them,
>> >> and rarely use Open Office myself.)
>> >
>> > I have seen that on Windows.
>>
>> On Linux OOO is a single instance multiple window application. And I
>> can't get it to load the same document in more than one window anyway,
>> it just raises the window where the document is already open?
>>
>
> You run the other copy of OpenOffice on another workstation.
>
> Chris

Ok, understand.  OOq puts a lock file in the directory for each file
thats open, thats how it prohibits multi-edit.

Thats Ok for a document editor, but I'm not so sure for a development
editor where potentially lots of files are open.  And the performance
hit on remote files is potentially significant.  Users editing remote
files are already complaining about performance.  And we then have the
problem of removing lock files when Geany quits or crashes.  That
means blocking closing Geany until lock files are removed which could
be a problem again on remote filesystems.

Cheers
Lex

>