furikuri

u/furikuri@programming.dev
5 posts · 43 comments

Recent posts

Recent comments

on Dev Interviews · c/programmer_humor · 2 pts · 1y

Honestly, for the first year or two after learning about it (which is the only time where it's really relevant) that's exactly what I did. Spend 30 seconds, derive something that's definitely correct, and never worry again about your memory randomly failing you

See the current dislike for fully digital display on cars. As they are now they just seem like a imprecise replacement for the function keys that either forces you to constantly look down at them (since the main selling point is that programs can change it at will) or force map them to F1-F12 (meaning you've spent extra on the touch-bar for no reason)

on I'm Guilty as Charged · c/linuxmemes · 7 pts · 1y

Run info info

Texinfo pages were originally meant to be a longer alternative to manpages that had support for featureful navigation (links, indexes, etc). They're nice and I can see a world where they did catch on, but the standard viewer is always a little bit of a shock to jump in to (being based off Emacs and all)

For cases where you really just want to jump between different prompts without piping out to another program/file, many terminals also support jumping through prompts as long as your shell marks them with an OSC-133;A escape code (looks like fish does this automatically now). Some terminals that support this are foot, tmux, kitty, and Emac's vterm, but it's undoubtably available in many others.

For example let's say you're using the foot terminal and the zsh shell. Just add the following code to your zshrc and then you can jump through each prompt using CTRL-z and CTRL-x

precmd() {
    print -Pn "\e]133;A\e\\"
}

Lmao. They couldn't even copy code from a random MIT licensed project? Sometimes I think these scammers aren't even trying

Arch does tend to keep packages as close to upstream as possible, which can be both a good and bad thing. Sway not binding to graphical-session.target by default is a little strange for example. Other distros also save a first-time user a great deal of configuration for things they probably don't care about as well. Going through Fedora's install and finding out that disk encryption and SELinux were configured OOTB was very nice to see personally. On the other hand Arch's installation (w/o archinstall) has you choosing a bootloader, audio server, display manager, etc. Nothing arduous and I like it, but definitely not for everyone

This is all eliminated by spinoffs of course, but even there users have the option to run random scripts/AUR packages without vetting them. Also doesn't help that the most popular Arch-based distro for a while (Manjaro) was pretty flaky and generally incompatible with the AUR (despite saying otherwise), leading to many people saying "that's just Arch" and swearing off the parent project as well

on How to quit VIM? · c/linuxmemes · 2 pts · 1y

I switched to (Doom)-Emacs from a ~7yr old homegrown Vim config last week and honestly the configuration is less bad than it seems. If you're mainly writing markdown you'll probably get 99% of the way there by just enabling the dedicated module

If I had to guess I'd say that their other project, Sponserblock, got a little bit more popular than they were expecting and this is just to help alleviate server costs. Most of the API endpoints don't require any auth at all (the single one that does accepts a random UUID), so any checks must be locally done (maybe system time?). The extension and server back-end are licensed under GPLv3 and AGPL respectively and are also entirely self-hostable, so the code is out there to verify if you wish

Additionally if you're looking for it to start on boot without logging in, you might find the loginctl enable-linger command to be of use. Maybe along with a Restart=on-failure policy in the service file if this is for a headless unit or something