Shell Scripting

1349 readers

4 users here now

From Ash, Bash and Csh to Xonsh, Ysh and Zsh; all shell languages are welcome here!

Rules:

Follow Lemmy rules!
Posts must relate to shell scripting. (See bottom of sidebar for more information.)
Only make helpful replies to questions. This is not the place for low effort joke answers.
No discussion about piracy or hacking.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!
These rules will change as the community grows.

Keep posts about shell scripting! Here are some guidelines to help:

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)

In general, if your submission text is primarily shell code, then it is welcome here!

founded 1 year ago

MODERATORS

[email protected]

What are the most inscrutable lines of $SHELL you've ever written? (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

48 comments fedilink hide all child comments

I'm sure some of you have absolute monstrosities of sigils (I know I do, in my .zshrc alone). Post them without context, and try and guess what other users's lines are. If you want to provide context or guess, use the markdown editor to spoiler-tag your guesses and explanations!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago

reply=( ${(M)dirs:#*/$~pattern}(Noe['REPLY=${(l[3][0])#REPLY:t}'][1]) )

Literal explanation

$~pattern interpret globbing characters (like *, ?, or [a-z]) in the parameter $pattern,
${(M)dirs:#*/$~pattern} filter the array $dirs to those matching */$~pattern.
${...}(...) everything in (...) are globbing qualifiers
(N) enable nullglob
(oe[...]) sort by the result of the shell snippet, where $REPLY is used as input and output
${...REPLY:t} remove all leading path components from $REPLY
${...#REPLY:t} substitute the length of that string
${(l[3][0])#REPLY:t} left-pad with zeroes to a length of 3
reply=( ... ) save as $reply

Full context

This line is in a function which dynamically expands ~[g:abc] to one of my git repos, choosing the shortest directory matching path/to/abc*, or if no match is found, the shortest matching *abc*. So between /long/path/to/abcdef and /short/abcdefg, it would choose the first one (provided both of those were in the search paths I configured).