On Tue, May 25, 2010 at 11:24:04PM +0200, Julien Guertault wrote: > Good evening (or else for those not in Europe), > > On Tue, May 25, 2010 at 22:20, Thomas Adam <[email protected]> wrote: > > On Tue, May 25, 2010 at 09:55:05PM +0200, Jean Felder wrote: > >> In fact, I'm launching emacs daemon at startup with the command "emacs > >> --daemon" > >> Then, I'm using "emacsclient -c" > >> The first time, I'm using emacsclient, the window is launched but not > >> maximised. > >> The second time, everything works fine : the second window is maximised. > >> > >> Perhaps, this is emacs related. > > > > Almost certainly. ??I refuse outright to install emacs on my machine, > > Emotional issue detected. :) > > > > but I suspect what's happening here is that the emacs client window > > is maximized by FVWM, but something is then undoing it. > > I don't know much about emacs' internals, but I have noticed a couple > of times that sometimes, when I maximize it manually before it is done > initializing, it would get back to a window size (without letting the window > manager know: it will still be considered maximized).
Yes -- because it seems the emacs folk think that: src/frame.c:x_figure_window_size() ... is a really good thing to do. That's the problem -- somewhere in that monstrosity of a function is the reason why the window size is reset. But that's as far as I dare dig into emacs' source code. Time to go and ask the emacs' people why they changed the behaviour between 22.x and 23.x, and what you, as a dedicated and loving user of emacs, can possibly do about it. Nothing FVWM can do to help you. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
