[Geany-devel] altername session management implementation

Lex Trotman elextr at xxxxx
Thu May 20 11:23:49 UTC 2010


On 20 May 2010 20:50, Dimitar Zhekov <hamster at mbox.contact.bg> wrote:

> On Thu, 20 May 2010 20:32:37 +1000
> Lex Trotman <elextr at gmail.com> wrote:
>
> > > No, no. The .geany files names used include the SM client id, which is
> > > unique for each program (normally UUID-s).
>
> small mistake: s/.geany files/.conf files/
>
> > > The whole idea is that each Geany saves itself, without any relation
> > > to the other running Geany-s.
> > >
> > Ok, I see great,  so when the X session re-starts all the Geanys re-load
> > ok, but then what happens if I shut Geany instances down manually?
> >
> > Somewhere a non-session geany.conf must be written, does the last shut
> down
> > win or what?
>
> When you stop a geany with [x] or File -> Quit, it's no more part of
> the x11 session, so the SM executes it's discard command, which
> removes it's geany-smclientid-conf file.
>
> Aside from that, the standard geany quit is unaltered. It does what it
> ever did.
>
> Ok, in Eugenes version only one Geany, the first one run, will save the
Geany.conf so you know what you will get next time you start a Geany, does
your version allow all Geanys to save their geany.conf, ie last closed
"wins"?

Your session management feature sounds great, lets each instance of Geany
set the config it wants, but I'm just trying to understand how it works with
the rest of Geany and when I change what instances are running.

I'm not really fond of last wins, though it is common on Unix.

Oh yes how does your patch work if the X sm libs are not available (eg
Windows), can we set a symbol to compile without it?

Cheers
Lex


> --
> E-gards: Jimmy
> _______________________________________________
> Geany-devel mailing list
> Geany-devel at uvena.de
> http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geany.org/pipermail/devel/attachments/20100520/f121be6c/attachment.html>


More information about the Devel mailing list