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.

Yeah, I’ve been using it for about a year now. It’s a little frustrating that it will learn my misspellings before it suggests a proper replacement, but otherwise I have no complaints. Direct upgrade over the stock AOSP keyboard.

The entire post was off-topic as FUTO does not qualify as open source. That being said, the mods should probably update community rules instead of murdering a discussion thread.

Removed by mod

Why is open source dogmatic? Because every line of code should have a purpose. Features are inherently optional and often cloud the project from the initial objective.

Few people are paid to maintain this category of software so they want to keep things manageable. Omitting features is the easiest way to limit edge cases and keep up with your dependencies.

I’m the same way. Honestly I just like the built in terminal emulator for those few times I forget to open tmux first. Not a fan of the lua integration. Makes the initial startup slower for my config.

Sorry, it was, just not for exploring all of those instances at once. Should have called out the tiling function. Screen also built in a serial terminal emulator and started playing with a few other things.

Executing a command, capturing all terminal formatting and escape codes so I can do some light manipulation on leading whitespace before dumping it back to the terminal.

Tmux was purpose built for terminal multiplexing. You can assign session names for organizing and manipulating multiple instances. Send keys to and read output from detached sessions. It’s easy to script.

People always sleep on script. It’s badass and let’s you do goofy things like this while keeping standard terminal formatting: https://github.com/StaticRocket/dotfiles/blob/043e9a56cc9515060188ec4642e4048c0dd6c000/dot_bashrc#L79-L94

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.”

+1 to caddy. There are some services that set safe headers following the recommendations outlined by Mozilla but others don’t control headers as strictly. Caddy is the only web server that I found that supports loose default header values. These values will be selected unless the upstream application specifies their own values.

You can do something similar in nginx but it requires playing with maps and has a little more indirection than I’d like.

Just wish caddy was capable of starting as root and stepping down permissions like Nginx. I have certs being managed by other tools and have to make sure they are installed and chowned for caddy’s use when they are cycled.

Yeah, there are a lot of bells and whistles and a fundamental difference between the way they intend to manage dotfiles and the way stow does. Makes it difficult to get started.

One thing that helped me when I was first getting into it: Chezmoi doesn’t like compartmentalization like stow. It supports it, but it want’s you to lean into the config langue a bit before you start doing that.

If you do that you can get away with only touching the add, cd, and update commands.

I liked stow, and used it for quite some time. That being said, it has issues. Issues community members have attempted to solve. Issues the sole maintainer wasn’t addressing for quite a few years.

I use chezmoi now. I’ve still got mixed feelings, but the templating system is neat. Stow seems to have gotten out of it’s slump while I was gone. That’s good news! Anyone know if they addressed the tree specific folding/unfolding config feature? Not seeing anything in the docs…

https://man.archlinux.org/man/extra/xdotool/xdotool.1.en

https://man.archlinux.org/man/extra/wtype/wtype.1.en

Pipe your clipboard contents through either of those depending on your windowing system. I’d recommend putting that in a script and binding it to a keyboard shortcut.

Llvmpipe is enabled in mesa at compilation time and actually modifies the swrast_*.so the last time I checked. Not runtime configurable. Also, I know at one point it had issues running on 32 bit machines. Not sure if that’s still the case.