furikuri

joined 2 years ago
[–] [email protected] 2 points 3 weeks ago

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)

[–] [email protected] 1 points 4 weeks ago

The classic rm -rf $ENV/home where $ENV can be empty or contain spaces is definitely going to hit someone one day

[–] [email protected] 4 points 1 month ago (3 children)

"Glazing" is slang for over-complimenting, often to an obsessive degree

[–] [email protected] 5 points 2 months ago

Remnant of the type of keyboard that Emacs was developed on. Also the same place that the Super, Hyper, and Compose keys originate from

You can map it through your X server/Wayland compositor, but if not Emacs recognizes Alt and Esc as valid meta keys

[–] [email protected] 9 points 2 months ago

Guess the Hyper key is due to make a comeback!

[–] [email protected] 3 points 2 months ago

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\\"
}
[–] [email protected] 8 points 7 months ago

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

[–] [email protected] 5 points 7 months ago* (last edited 7 months ago) (1 children)

You could try making enabling git's rerere functionality, which stands for "reuse recorded resolution"

https://git-scm.com/book/en/v2/Git-Tools-Rerere

https://stackoverflow.com/a/49501436

[–] [email protected] 6 points 7 months ago (1 children)

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

[–] [email protected] 2 points 7 months ago

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