Or override the TERM variable in your ssh config. Setting it to an xterm value has been supported by any niche term I’ve used over the years without sacrificing any of the usual functions.

Arch. Started using it in high school. Never had a reason to switch. Now I’m just regularly frustrated by other distros trying to make things easier by abstracting simple configurations behind layers of custom scripts.

AUR, when I can. I run my own binary package repo. App images are an interesting concept, but usually they are compiled against ancient versions of glibc for increased compatibility. Optimizations and CVE patches may or may not be applied, LD lookups are longer, etc.

Sway still primarily counts as a WM + Compositor, but considering it has keymaps, autostart, and libinput config mechanisms embedded in it, I would say it borders a desktop environment.

The inhibit_idle specifier is cool, thanks for the pointer. This two liner can be replaced with:

for_window [all] inhibit_idle fullscreen

Please people, these stand alone guides are fine but continual use of the wiki ensures it is kept up to date. These should not act as or be used like a substitute.

https://wiki.archlinux.org/title/Linux_console/Keyboard_configuration https://wiki.archlinux.org/title/Xorg/Keyboard_configuration

The real problem: Define beginner distro

Every user is starting from a different point. There is no such thing as a beginner distro. You can say this distro is good for people who can grasp the idea of a command line or this distro is good for people who have no idea command line interfaces exist, but that doesn’t differentiate between beginner friendly or not.

I’d recommend tmux for that particular use. Screen has a lot of extras that are interesting but don’t really follow the GNU mentality of “do one thing and do it well.”