Arun Isaac writes:
Hello,
>> My suggestion is simple: remove the added layer of complexity introduced
>> by the .exwm file; don't force a default Exwm config on the user.
>
> I think I agree with you now. I checked, and exwm indeed does not run
> when emacs is opened in the console even though my exwm config is
> defined in my ~/.emacs.
Interesting. So the extra, unneccesary initialization code does not
hurt there.
I just tried adding my ~/.exwm into my init.el and running a nested
emacs and now I get a GUI dialog:
Replace existing window manager? Y/N
Not great! Not very suprisingly, the extra unnecessary initialization
/does/ hurt here.
> So, I see no reason to continue having ~/.exwm. If no one else has any
> objections, please do send a patch fixing this.
I would very much like for this nested emacs issue to be addressed
first.
I just don't really see the point in mixing two bits of code that are
meant to run in different scenarios, and then disabling one of them.
Greetings,
Janneke
--
Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
