New post: shell tricks that aren't exactly secret, but aren't always taught either.

[larvitz@burningboard.net]

New post: shell tricks that aren't exactly secret, but aren't always taught either.

Split into two sections: what works on any POSIX sh (FreeBSD, OpenBSD, Alpine...) and what's Bash/Zsh-specific. Because not everyone is on Linux with bash as their login shell.

Things like CTRL+W, $_, pushd/popd, fc, set -euo pipefail caveats, and more.

https://blog.hofstede.it/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/

#unix #bash #shell #sysadmin #freebsd #linux #cli

[havarpan@mastodon.bsd.cafe]

@Larvitz I recently learned a funny trick from Kirils Solovjovs in a bash workshop. He had in his path a script called `\#` that he used to comment out pipe elements like `mycmd1 | \# mycmd2 | mycmd3`. This was how the script was written:

```
#!/bin/sh
cat
```

[lutzhuehnken@mastodon.social]

@Larvitz I often use "Meta+." (in your config: ALT+. I guess) to get the last argument of the last executed command.

[joel@gts.tumfatig.net]

@Larvitz side note, I don’t think OpenBSD has POSIX sh. Quoting the man page

This version of sh is actually ksh in disguise. As such, it also supports the features described in ksh(1). This manual page describes only the parts relevant to a POSIX compliant sh.

Just saying as I got caught thinking my scripts were POSIX compliant on OpenBSD and failed when running them using FreeBSD sh ‍️

[larvitz@burningboard.net]

@joel thanks for the hint. I actually wasn’t aware of that! Always thought it’s defaulting to a korn shell.