Jan Nieuwenhuizen <jann...@gnu.org> writes: > André A. Gomes writes: > >> Jan Nieuwenhuizen <jann...@gnu.org> writes: >> >>> 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. >> >> Isn't exwm doing precisely what it's supposed to do? Isn't it fair that >> the newly spawned (nested) Emacs has the right to take control over the >> "older" Emacs? > > Of course; that's my point exactly! Emacs cannot know, and thus cannot > help but doing the annoying thing: throwing a dialogue. That is what > this code > > (cond ((file-exists-p "~/.exwm") (load-file "~/.exwm")) > ((not (featurep (quote exwm))) > (require (quote exwm)) > (require (quote exwm-config)) > (exwm-config-default) > (message (concat "exwm configuration not found. " > "Falling back to default configuration...")))) > > helps to prevent in a very nice way. Let's please keep it!
After all the effort I put into all of my previous messages, it's unfortunate to receive such a reply. I packaged EXWM (the right way) for myself a long time ago. If I'm putting effort into this, it's because I think the community is missing an opportunity to improve. I won't get anything from any of this. You, on the other hand, seem to be interested in your selfish agenda. Your reply indicates that little or no effort was put into understanding my points. And no effort was put to indicate where did my reasoning go wrong. I give up. Let "worse is better" reign. -- André A. Gomes "Free Thought, Free World"
