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

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…

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

It’s fine. Only issues I’ve had is occasionally some modifications to glibc will break anticheat but that’s only happened to me twice in the past 8 years.

I’m curious. There was some i2c connected memory devices before. Is there some forgotten spec that allows for a flexible device lookup / logging capability. Something that acts like device tree but stays specific to the bus. It wouldn’t be practical for a lot of applications but I could see it being useful for some niche stuff.

I2C is a bit goofy though. As a byproduct of being an undiscoverable bus you basically just have to poke random addresses and guess what you’re talking to. The fact lmsensors i2c detection works as well as it does is a miracle. (Plus you get the neat issue where even the act of scanning the bus can accidentally reconfigure endpoints)

WebSub (formerly PubSubHubbub). Should have been a proper replacement for RSS with push support instead of polling. Too bad the docs were awful and adopting it as an end user was so difficult that it never caught on.

Or just use virtmanager + libvirt

I’m glad the Brits are finally getting it. We’ve had colord for a while now…

Looking at fully riced desktops like https://piped.video/watch?v=0KdDfGHpl5M&t=66

TempleOS a passion project? Feels like a little bit of an understatement…

It’s a function of PPI, hinting settings, font face, etc. The both of you can be correct in your own right…

Objectively there is a long history font rendering issues under linux though, so… eh.

Dog. I’m an arch user. You can’t just say “Arch is easier than Debian” and then in the first part of your argument say:

Yes there is the apt repository but if you want something that’s not in there, get ready to read the documentation or follow random guides.

You do realize Arch just frontloads that effort right? It’s not any “easier.” We embrace the removeding manual. (Arch based distros aside…)

Now if you were praising the simplicity of makepkg and the PKGBUILD syntax then sure. As is, though, this is just a bad take.

This is where someone tracks down an upgrade path chart you didn’t know existed and points out some goofy intermediary release, not an lts for some reason, that you were supposed to upgrade to first…

Yep, from kernel/ksysfs.c

/*
 * Make /sys/kernel/notes give the raw contents of our kernel .notes section.
 */