This will happen more or less often depending on the kinds of tasks you do with Emacs. Which can of course be customized to death, but is not particularly great for large numbers of windows, in my opinion.Īnother problem with EXWM is that if Emacs hangs for any reason (e.g., waiting for TRAMP to open a remote SSH file, or syntax highlighting choking on an overly long line in a JSON file or a Python shell), your whole graphical session freezes, because EXWM does not get an opportunity to react to X events while Emacs is hung doing other stuff.

EXWM does not really do much in the way of managing windows: essentially, EXWM just turns all your windows into Emacs buffers, and the window management tasks proper (splitting, deciding which Emacs window will display a new X window, etc.) is the built-in window management Emacs uses for its own windows. So here I am.ĮXWM has a lot going for it, mainly from the fact of running in Emacs, and therefore benefitting from the general powers that all things built on Emacs have: it's eminently hackable and customizable (and you can generally see the results of your hacks without even restarting it), and can be integrated in your Emacs workflow in various ways (I gave some examples in my previous EXWM post). This time, after a long time using EXWM (which I picked up more easily at the time since all the commands were the regular Emacs window/buffer commands I already knew), i3 was quite easy to pick up. I had actually tried i3 years ago, but I had never used a tiling window manager before, and for some reason it didn't click for me at the time. And after two weeks using it, I have to say I'm definitely sticking with it.

Tags: comp, unix, wm, emacs, in-englishĪfter almost 3 years using EXWM as my window manager, I decided to give i3 a try.

Switching to the i3 window manager 16:00 +0100.

I3 window manager mac