every so often I get confused because I'm writing a zine about the terminal and didn't I already write 4 zines about the terminal???

but I've never written about what the UI “rules” you need to know to use the terminal interactively are, only:

- notes on core Unix concepts — file descriptors, signals, etc (Bite Size Linux)
- shell scripting (Bite Size Bash)
- cheat sheets for sed/grep/xargs/etc (Bite Size Command Line)
- cheat sheets for command line networking tools (Bite Size Networking)

I haven't totally sold myself yet on this "what are the secret rules of the terminal?” framing but it feels like a reasonable way to talk about how, even though “the terminal” is a lot of separate things working together, it "feels" like a cohesive environment that has a lot of rules that you can generally expect to be true.

Some of those rules are Unchangeable Facts and some of them are just Vague Social Rules but understanding the vague social rules is just as important as knowing The Facts.

an example of a "social rule" in the terminal is that if you have a noninteractive program, you can generally expect that `Ctrl-C` will stop it, programs can do whatever they want but it would just be kind of rude for a noninteractive program to not respect `Ctrl-C`

(there are different and more complicated social expectations around how to quit interactive programs)

another example of a "social rule" is that at an interactive prompt you should expect `Ctrl-W` to delete the last word, this is weird because depending on the _kind_ of program, the exact mechanism for how `Ctrl-W` will delete the last word might change, but I think it would be generally considered rude if a program with an interactive prompt treated `Ctrl-W` in a different way

(text editors are an exception though and generally are allowed to handle text editing however they please)

@b0rk Is it still a social rule that terminals respect control-S/control-Q flow control? I helped a lot of people “unfreeze” their terminals back in the day after they fat fingered their way to sending a control-S!
@dwenius i think so? personally I've been using fish for the last ~10 years which disables Ctrl+S completely by default so I don't have much of a relationship with it personally
@b0rk Aside: have you shared your fish config and functions anywhere? I’d be interested to see how you set things up, as I keep bouncing off of fish despite it seeming like just my kind of thing…
@dwenius I basically don't configure fish at all (other than aliases, PATH, and some environment variables) but I wrote a blog post about why I like it! https://jvns.ca/blog/2024/09/12/reasons-i--still--love-fish/
Reasons I still love the fish shell

Reasons I still love the fish shell

Julia Evans
@b0rk Brilliant, thank you!