This is cool. Also, there is one little trick you can do to make your shell history easier to search. You can comment your commands and then search via comments:
% big hairy command here # foo the bars!
Then you can history search for 'foo' or whatnot. That doesn't totally obviate the need for a tool like this. I plan on checking it out.
Not too interested in the snippet manager, but when I was watching the demo movie, I noticed the author doing inline shell variable expansion. It never even occurred to me that shells could do that. Wish I had known about this years ago.
The day we know a language has made it is the day people no longer feel the need to suffix "written in X" to attract clicks.
This applies to Go, Rust, whatever. I'd love to see future projects stand on their own merits and be pleasantly surprised when discovering the source language on my own.
It can make a difference. For example, if this was written in ruby I might not bother using. On every device I'd have to get the correct ruby environment setup, install any dependent gems, and make sure if I have the gem path set correctly.
If it's written in go I know I can drop a static binary in my PATH and be done.
That's cool! I was thinking of doing something similar a few weeks ago. I settled on using tools I knew well to just achieve what I needed quickly. I use tmux and emacs. I run a tmux session with a window which has a top and bottom pane. Top pane shows a shell, and bottom pane shows emacs. Thanks to tmux, I can send keystrokes to a different pane. With emacs, I tell tmux to send the current line of characters to the top pane. In the emacs session, I have open a help.org file, where I organize some commands. For some reason, this worked with tmux 2.1 but not with tmux 2.3:
> [...] it is difficult to search them from shell history. There are many similar commands, but they are all different.
I think there's a much simpler way to go about this. Just add a snippet by typing it in your shell followed by an echo command, e.g.:
ls -rt; echo "List all files reverse-sorted by date"
Then the problem remains to search your shell history, but there are many solutions for that already. And the good part is (besides not needing another tool) that you can search the same way for commands that were not labeled with a description.
If you feel like working on something like that, see my comment in this thread about Borg. We are pretty far ahead in the development, and happy to get contributors.
We have 4 members in the team but there are loads of work to do.