Bash, just because everything else already uses it. That and bashisms have infected nearly all of my scripts as I clumsily bump into the limitations of POSIX string manipulation.

I have found some very fun things with sed branching patterns as a result of these limitations though...

https://www.gnu.org/software/sed/manual/html_node/Branching-and-flow-control.html

That's my first thought, but my brain keeps trying to inject one immediately following "Surely." No idea why.

I feel like there needs to be a comma somewhere in that sentence but I don't know why...

Unfortunately this doesn't seem to apply to publishers or developers that don't have a landing page

Depending on the launcher and launch method you may need to set systemd variables. Look at the way 50-systemd-user.conf works https://wiki.archlinux.org/title/Sway#Configuration

I use the following fragment to make sure the cursor theme propagates to applications launched with wofi: https://github.com/StaticRocket/dotfiles/blob/main/dot_config/sway/systemd-user.conf

Some of them advertised specific performance improvements.

I'm not going to rag on them though. Some of them did have performance improvements and basically created the tools and optimized defaults that propagated to standard distros, allowing the gap to close.

For people using bash that are thinking "how do I do that":

The bash-complete package adds the _command function for recursive completion on commands that accept other commands with their own arguments. It's what sudo uses last I checked. You can add complete -F _command stfu to your bashrc to link it to the stfu command.

https://man.archlinux.org/man/bash.1#Programmable_Completion

I don't get people being worried about an offline application designed to run one shot as the current user not receiving updates. I do get maintainers dropping the package from package repos now that it is officially archived though...

Googles requirements for ARM cores on Android was pretty high. Don't think I've seen a RISC-V core get close yet...

Cool, saw your logs just a while ago with the error about being unable to execute /bin/sh so I figured as much. What did you do to get there? I've never had an update fumble that hard...

Try rolling back that comment kiddo

https://wiki.archlinux.org/title/Snapper#Wrapping_pacman_transactions_in_snapshots

That warning comes up if you are using sd-vconsole but do not have systemd in the mkinitcpio hooks. You should fix that but it is most likely unrelated to the login issue.

Login issues normally hint at either the user shell or pam configs being wrong but you can also get this behavior if (the users home directory is on a secondary disk && that disk failed to mount && you aren't using systemd-homed).