11–20 of 49 posts
This seems like it can help do the same thing more quickly, so I'm keen to give it a go.
I do like shell history though, a shame to just have a bunch of `navi` entries - I wonder if it could be faked; populated with the chosen command afterwards?
navi allows you to browse through cheatsheets (that you may write yourself or download from maintainers) and execute commands, prompting for argument values.
Combining both cheatsheets and a better UX is brilliant. Wish I had this years ago when trying to wrap my head around the shell.
navi allows you to browse through cheatsheets (that you may write yourself or download from maintainers) and execute commands, prompting for argument values.
Once I tried a tool like this, but just realized, there is already a method of that: the ~/bin folder. You can write bash scripts, or scripts in any programming language with the proper shebang line, you can download other people's scripts, and you don't need bash history to keep them. Listing all of them is just an ls. I tend to not put file extensions of them and use good naming, so you can see everything without l…
> Once I tried a tool like this, but just realized, there is already a method of that: the ~/bin folder. One thing I'd add to this is that "crib notes" can be captured in man[0] pages. For example, having them in $HOME/man and ensuring MANPATH[1] includes it serves as a nice complement IMHO. There seems to be a markdown-based tool[2] which can assist in authoring them too. EDIT: It looks like pandoc[3] can generate m…
Wow, this is really cool. I assumed this was going to be written in go or rust, but taking a look it's actually all bash! I'm always surprised by how much people can get out of bash. It's also some of the cleanest bash I've seen. Definitely going to be using some of these patterns for my own scripts.
Once I tried a tool like this, but just realized, there is already a method of that: the ~/bin folder. You can write bash scripts, or scripts in any programming language with the proper shebang line, you can download other people's scripts, and you don't need bash history to keep them. Listing all of them is just an ls. I tend to not put file extensions of them and use good naming, so you can see everything without l…
This is why I have a similar tool for command line cheat sheet snippets - recalling bits of syntax to be combined into a command or a script.