[zsh]$ ls -l *(Lm+10om)
zsh supports extended globs, this says: -l give me a long listing
“*(…)” of any file
Lm+10 who’s size “L” in megabytes “m” is greater than 10
“om” ordered by modification ascending [zsh]$ ls -l *(Lm+10om)
zsh supports extended globs, this says: -l give me a long listing
“*(…)” of any file
Lm+10 who’s size “L” in megabytes “m” is greater than 10
“om” ordered by modification ascendingIt’s of course possible to do with existing shells, but it’s impossible to argue that it’s a clear
Or are you optimising for getting your thoughts transcribed to the machine as quickly as possible. It’s usually this case for me.
I tend to maintain a huge shell history so i really like the terse format for quickly filtering down my historical commands.
Writing shell scripts might be a good case for the longer form style although bourne-esque syntax is burned into my fingertips after all these years that long form is not going to be useful to me.
But sure, there’s a tension between readability and brain-to-command throughput that’s always been there.
The way you proposed is a bit too write-only for my taste, and the argument that you “had to learn it and now you’re muscle memory bound to it” is applicable to you only and does not preclude a better way from existing.
I put #tags at the end of long, opaque, reusable commands so that I can FZF search it quicker.
This globbing functionality in zsh is separate from the ls command, so no ls magic here, but the ls builtin in zsh does have some useful extras in it all the same