My zsh shell files are at over 3000 lines of code, not including 16 plugins of various complexity.
Having built that up over the course of many years, I decided it would be interesting to see what the “best” Zsh config I could write with some constraints.
[Read More]There is a very cool and useful tool out there called
Ultimate Plumber.
You call it with some-command | up,
and then it opens a simple TUI where
you write a pipeline at the top of the screen
and see results of some-command piped through that pipeline
beneath it.
It is such a wonderful tool for working with pipes, but there is one problem I have: it doesn’t use the Zsh line editor.
[Read More]I recently (re)discovered the Oil shell. The last time I saw it, it was trying to write a language to subsume Bash, Awk, and Make.
However, I came back to it doing nearly accomplishing two smaller goals:
osh) as close to Bash-compatible as possible.oil).And I really like it.
[Read More]tl;dr: Always use the flags -D and -E (and -F if available).
Add a colon to indicate an argument is required
(similar to getopt)
After a busy weekend of visiting siblings, car troubles (snow’s no joke) and getting back to school, I had a chance to sit down to work on my #100DaysOfCode project.
I saw the Geometry zsh theme hit 2.0! It looks like a more modular Pure, which is fantastic for me!
With that, I figured it was as good of a time as ever to rename and rebrand my prompt segment to be more prompt-agnostic. I now have instructions for enabling it with Geometry, P10k, and Bullet Train.
Check out Using zparseopts
Wrote more of the zparseopts post, I think I have everything explained.
Waiting until I look over it more tomorrow,
see if I worded anything poorly.
Wrote most of a zparseopts post, I’ll be putting it up here soon.