this post was submitted on 02 Apr 2024
82 points (95.6% liked)

Unixporn

15392 readers
1 users here now

Unixporn

Submit screenshots of all your *NIX desktops, themes, and nifty configurations, or submit anything else that will make themers happy. Maybe a server running on an Amiga, or a Thinkpad signed by Bjarne Stroustrup? Show the world how pretty your computer can be!

Rules

  1. Post On-Topic
  2. No Defaults
  3. Busy Screenshots
  4. Use High-Quality Images
  5. Include a Details Comment
  6. No NSFW
  7. No Racism or use of racist terms

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
82
[Sway] Lisp is taking over (programming.dev)
submitted 7 months ago by [email protected] to c/[email protected]
17 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 7 months ago* (last edited 7 months ago) (1 children)

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)

[–] [email protected] 1 points 7 months ago (1 children)

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.

Mickey Peterson wrote an article on how Emacs manages its own windows, and the Elisp Manual on Windows is pretty good too.

[–] [email protected] 2 points 7 months ago

Correction: it's

emacsclient -c -e '(elfeed)'

The -c flag seems important, as it creates a new frame (a new window)