>>67
All those programs you use on linux except for dwm can be ran with fbcon/tty equivalents. Unless you use real graphics from emacs or like how mupdf navigates.
Don't forget guix is a more do it your self and integrate others work more then nix and port*. You need to override the xorg service module here.
mono-threaded emacs
This is false but the now mainline threads is shared concurrency and not truly parallel, if you don't know this you probably aren't at the level needed for using exwm or xwem as a daily drive, much like getting around what crashes c compiz don't remind anyone of this you must get around what stalls emacs.
Before emacs 24 concurrency was """a hack""", observe this xelb comment for a classic implementation.
;; How it works
;; ------------
;; As is well known, X11 is a network-transparent protocol. All its messages,
;; including requests, replies, events, errors, etc are transported over
;; network. Considering that Emacs is powerful enough to do network
;; communication, it is also possible to use Emacs to send / receive those X11
;; messages. Here we fully exploit the asynchronous feature of network
;; connections in Emacs, making XELB concurrent in a sense.Now I do remember that not everything in nonelisp emacs is threaded yet and some of the elisp isn't concurrent yet, so you can get stalls for some simple tasks, what you do for this is multiple emacs gnuservs or frames, depending on what's stalling.