Yes! Emacs has already taken over most of my desktop environment apps with the exception of the web browser and a few apps like Blender and Gimp. I haven’t gone as far as you, getting each Emacs buffer to display in its own frame in is own WM-level window, but that would make for a more immersive experience. Also, your color scheme is similar to the one I use now. I love it.
I can’t wait for the day when software written in Lisp takes over my window manager, then my panel, then my session manager, then my whole operating system kernel.
That might work if I re-bound the split-window function to launch a new Emacs client, because this is the function that most other Emacs functions use to split the frame into windows.
But I think a better approach would be to just add a single rule function into the display-buffer-alist that always asks for a new frame no matter what the input is.
![[Sway] Lisp is taking over](https://programming.dev/pictrs/image/c1051a9c-c304-414c-a834-1f78ad5f347e.png){kind=link}
Yes! Emacs has already taken over most of my desktop environment apps with the exception of the web browser and a few apps like Blender and Gimp. I haven’t gone as far as you, getting each Emacs buffer to display in its own frame in is own WM-level window, but that would make for a more immersive experience. Also, your color scheme is similar to the one I use now. I love it.
I can’t wait for the day when software written in Lisp takes over my window manager, then my panel, then my session manager, then my whole operating system kernel.
If you want each of them to be their own window you can do a:
emacsclient -c -e '(elfeed)'to do that. (Note: not completely sure of the syntax but that’s the basic idea of it)
Edit: Added -c flag to create new frame (window)
That might work if I re-bound the
split-windowfunction to launch a new Emacs client, because this is the function that most other Emacs functions use to split the frame into windows.But I think a better approach would be to just add a single rule function into the
display-buffer-alistthat always asks for a new frame no matter what the input is.Mickey Peterson wrote an article on how Emacs manages its own windows, and the Elisp Manual on Windows is pretty good too.
Correction: it’s
emacsclient -c -e '(elfeed)'The -c flag seems important, as it creates a new frame (a new window)