Spyke

Replies

Comment on

Which one???

When in doubt, ~/.zshrc. It's the right choice 99% of the time. Otherwise, there's a chance you fuck up scripts you've installed which assume no shell options have been changed in non-interactive contexts.

Comment on

*Permanently Deleted*

Reply in thread

I grew up with Fahrenheit, but switched my weather app to use Celsius for a while, and I've internalized it pretty well. It works fine. The "human experience" angle doesn't work anyway because that experience is very locale-dependent.

linux

Comment on

Must fight temptation to buy an overpriced raspberry pi

Reply in thread

Yeah, theres a lot of old old laptops which make no sense to run. But there's a growing crop of more recent used devices that are only being sold off because they don't support Windows 11, and the power efficiency story changes there. The OOP mentions "8.1 lappies"; my main laptop has a 15W 8th gen which is only in the last year starting to feel less appropriate for desktop use. (And honestly, a RAM and storage bump will probably get me another couple years.)

For environmental concerns, youve got to tax new devices with manufacturing costs as well.

100% agree about VMs though.

linux

Comment on

Microsoft Edge, anyone?

I have it on Steam Deck since it can be launched with a CLI argument to force a 1280x800 window.

Vivaldi pretends to be Edge when visiting Bing to unlock GPT-4, and prefer that to Edge on my other devices. (Secondary to Firefox, ofc)

Comment on

Which one???

Reply in thread

Select the color which matches the steps before filenames ((non-)login and (non-)interactive), then follow that arrow the rest of the way. There's more colors in Bash because Bash makes a distinction between remote and local shells.

Another way to look at the same data for Zsh (note: $ZDOTDIR will be used instead of $HOME if it's defined at any step along the way):

Fileneitherinteractiveloginboth
/etc/zshenvxxxx
${ZDOTDIR:-$HOME}/.zshenvxxxx
${ZDOTDIR:-$HOME}/.zprofilexx
${ZDOTDIR:-$HOME}/.zshrcxx
${ZDOTDIR:-$HOME}/.zloginxx
${ZDOTDIR:-$HOME}/.zlogoutxx

One confusion on the Bash side of the diagram is that you see branching paths into ~/.profile, ~/.bash_profile and ~/.bash_login. Bash will use for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and execute only the first one that exists and is readable.

Comment on

Vim is built different

Reply in thread

I don't fit into any of those categories.

Its obtuse, old, and doesn't have a lot of functionality of modern code editors

Obtuse? Yeah. The keyboard focus means natural discoverability is low. But I immediately preferred modal editing once I learned it.

Old? Eh, most people use Neovim nowadays and write plugins in lua. Even in OG Vim, Vim9script broke compatibility for a better dev experience.

Functionality? Out of the box, it is just a text editor. But only VSCode might have a more active plugin ecosystem. ALE has been a thing for ages if it's LSP support you're looking for.

It's not better, it's not worse, I'm not in any way superior for using it, but I love it for a reason.

linux

Comment on

Make Ctrl+Arrow Keys the default?

I'm pretty sure both are possible in xkb. But you'll have to learn how to get a custom xkb_keymap into your DE of choice. I only learned enough to do one mapping:

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)" };
	xkb_types     { include "complete" };
	xkb_compat    { include "complete" };
	xkb_symbols   {
		include "pc+us+inet(evdev)"
		key  {
			type= "TWO_LEVEL",
			symbols[Group1] = [  Multi_key,                Caps_Lock ],
			actions[Group1] = [ NoAction(), LockMods(modifiers=Lock) ]
		};
		key  {[ Escape ]};
	};
	xkb_geometry  { include "pc(pc105)" };
};

This remaps Capslock to Escape, Escape to Compose, and Shift+Escape to Capslock. Not what you want, but hopefully this will give you a starting point to playing/breaking xkb.

Another benefit of doing this with xkb: it's now a separate codebase from X.org, and is used in every Wayland compositor I know of.