What are the most inscrutable lines of $SHELL you've ever written?

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I’m sure there’s a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

Gamma@programming.dev · edit-2 1 year ago

What are the most inscrutable lines of $SHELL you've ever written?

narshee@iusearchlinux.fyi · 1 year ago

I don’t have a riddle and I can’t read Bashisms. In posix shell the most unreadable things are parameter expansion, but compared to the lines OP posted they seems straight forward.