[–] 1 point 6 months ago (1 child)

A comparison to eat would be interesting - as it does not have external dependencies I generally use that, but there are a few things where it reaches its limits.

  • source
  • [–] 3 points 7 months ago

    Hi, I'm the author of this.

    There's currently very little user-facing documentation; in general you can imagine it to work approximately the same way as EXWM. Wayland windows (e.g. your browser) just become another buffer inside of a full-screen Emacs frame, and then you use the normal Emacs window management paradigm.

    This project is pretty new (river 0.4.0 just came out, and I wrote this originally two weeks ago, with last week being the first week where it was actually usable). There's a few more things I want to implement and clean up before I focus on making it more usable, right now the early users are mostly experienced EXWM-users and so on, i.e. people who don't really require any hand-holding. I think it makes sense to put off the "user-friendliness" until there's a certain level of polish and stability in the core features.

  • source
  • parent
  • context
  • [–] 1 point 7 months ago (2 children)

    Oh, this is neat.

    I do kind of wish that there was more of a summary of how it works on the page from a user standpoint. For example, the page links to niri, which the author previously used. That describes the basic niri paradigm right up top:

    Windows are arranged in columns on an infinite strip going to the right. Opening a new window never causes existing windows to resize.

    Every monitor has its own separate window strip. Windows can never "overflow" onto an adjacent monitor.

    Workspaces are dynamic and arranged vertically. Every monitor has an independent set of workspaces, and there's always one empty workspace present all the way down.

    The workspace arrangement is preserved across disconnecting and connecting monitors where it makes sense. When a monitor disconnects, its workspaces will move to another monitor, but upon reconnection they will move back to the original monitor.

    I mean, you can very quickly skim that and get a rough idea of the way niri would work if you invested the time to download it and get it set up and use it.

    It does say that reka uses river, and maybe that implies certain conventions or functionality, but I haven't used any river-based window managers, so it doesn't give me a lot of information.

  • source
  • [–] [S] 1 point 9 months ago (2 children)

    Some other young ones in irc:

    • [2026-01-18 17:01:33] I've used emacs since I was 13/14, 20 now
    • [2026-01-18 17:02:11] My girlfriend also used it for a solid while, she's 22
    • [2026-01-18 17:02:19] so I used Emacs when I was ~15-16 but really never learned it well, then didn't touch it for 7-8 years

    11's still the number to beat, if we're counting "playing the Emacs Adventure" (which of course we should).

    13/14's a solid young use.

    I think we're starting to show emacs is not just for "old brain".

  • source
  • [–] [S] 5 points 9 months ago

    I didn’t use emacs much until around 2014,

    Heh. I started using emacs in 2014, when an irc friend who had been using it for a decade were moving parts of their 10 year old config to a new one (iirc, they were moving to org-mode config), and then in 2024, I did the same, moved my 10 year old config over to an org-mode config.

    Anyhoo,

    but I remember playing the Emacs Adventure around 2006 when I was 11.

    1. Can we count that as the youngest yet?
  • source
  • parent
  • context
  • [–] 2 points 11 months ago

    Thanks for that. I shall have to try out Reader.

    I did watch the two LLM related talks and tried out editor-code-assistant as a result. It's really nice being able to play with the powerful agent based workflow directly in my favourite (only) editor.

  • source
  • view more: ‹ prev next ›