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}
If you want each of them to be their own window you can do a:
emacsclient -e '(elfeed)'to do that. (Note: not completely sure of the syntax but that’s the basic idea of it)
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)