commit 4935e81a65b7e615cccd1bae76a5459b9948b11a
parent a3c2fbacf5a5da6fb94a7705a5a0be4c56838f21
Author: Nick Moffitt <nick@zork.net>
Date: Wed, 20 May 2026 09:30:46 +0100
ANSI!
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/spacehobo.mdwn b/spacehobo.mdwn
@@ -53,7 +53,7 @@ _noop[0]='array accesses turn 0/nonzero into defined/undef!'
### Here's how we detect colour support
-Most terminals support the standard ANSI escape sequences now, but we still have to be careful. This catches ghostty, kitty, foot, and any terminal type with `color` in the name (such as `tmux-256color` or `xterm-256color-bce`).
+Most terminals support [the standard ANSI escape sequences](https://en.wikipedia.org/wiki/ANSI_escape_code) now, but we still have to be careful. This catches ghostty, kitty, foot, and any terminal type with `color` in the name (such as `tmux-256color` or `xterm-256color-bce`).
```
case "$TERM" in
@@ -62,6 +62,6 @@ case "$TERM" in
esac
```
-If it doesn't find your terminal in that list, and the system you're on has `ncurses` installed, then it will try to send a code for red text to `/dev/null` with the `tput` command, and keep you colour-free if that fails.
+If it doesn't find your terminal in that list, and the system you're on has `ncurses` installed, then it will try to send the code for red text to `/dev/null` with the `tput` command, and keep you colour-free if that fails.
# I just think it's neat!
