Re: Session Restoring All Windows on First Workspace

[Christopher Roy Bratusek <zanghar freenet de>]

Am Fri, 13 Aug 2010 04:33:16 -0400
schrieb Clinton Ebadi <clinton unknownlamer org>:

> Jeremy Hankins <nowan nowan org> writes:
> 
> > Clinton Ebadi <clinton unknownlamer org> writes:
> >
> >> After a week of figuring out how all of the new desktop magic works I
> >> have a working sawfish setup except for one thing: when I logout and
> >> login all of my window are restored on workspace 0.
> 
> > Theoretically, I could use some other session manager and get the same
> > results.  Any suggestions for a simple session manager that just manages
> > a session?  Ideally I wouldn't have to spend much time futzing with
> > it...
> 
> So it turns out that sawfish was actually not even starting properly!
> 
> After fixing things such that it was being started correctly... it
> bombed out with a weird error and unhelpful backtrace. After a bit of
> debugging and figuring out how the debugger worked... tada, I discovered
> the problem was in lisp/sawfish/wm/user.jl. The last bit consumes *all*
> command line arguments, and attempts to load anything it does not
> recognize as a file, or, if it does not exist, as a module. And thus
> sawfish died upon encountering "--sm-client-id".
> 
> I skimmed the librep manual about this and it does seem this is intended
> behavior... I don't like it, but perhaps something relies upon the
> destructive consumption of elements from `command-line-args'. If nothing
> does I think the correct thing to do would be adopt standard getopt
> semantics (and just ignore any unrecognized command line arguments under
> the assumption something else will parse them later).
> 
> I've attached a patch.
> 

Sawfish does now register properly (the message that sawfish registration timed-out does
not longer appear in my .xsessionrc)