I really like how the search feature shows the frequency of each entry. I've thought before it would be cool to see the most used commands of some of the more experienced folks I work with, though ideally it would be slightly more generic than exact commands - i.e. Different arguments would count for the same command.
Would love a system that analyses my shell command usage and recommend when I should link commands I often use in series and turn them into one line.
It’s more than just frequency analysis because it helps to remember what commands happened before or after. It also needs to be smart about when two commands are actually “the same thing” but with different flags or input filenames.
One of the most productive tools that I have is being able to search command history for commands typed in the current directory. It becomes a knowledge database. I rolled up my one, but I haven't seen any tool doing it, which surprises me. Perhaps the McFly tool mentioned here.
In addition to this, I think something that would help me a lot is being able to step back and forward through any history of commands that I'm experimenting with.
Great projects for everyone. I have one suggestion though.
TLDR can also make use of usage analytics in general to only extract those command from original man page and put them in noob friendly documentation. It can be done for every command or just those which doesn't have community contribution.
This looks really nice. You say you record the number of times a command was executed. I'm currently using FZF for ctrl-r search, and it's amazing, but one thing that bothers me is that I have some commands that I search for and use quite often, but then I don't need them for a while, they vanish from my history, and then I need them again.
Would the internal database of McFly keep often searched for commands from the past, even though they're out of the bash history?
I use this fairly regularly! If you don't know, you can type almost any command, e.g. `curl cht.sh/ls` and it shows you common usages of `ls` with a short description for each command
I'd like a command line tool that could transform `history` into a list of alternate tool recommendations. Bonus if it could also generate recommended aliases and functions according to your habits.
I think we should change the link to sort by votes all-time [1]. It's just fun to go through and see some of this stuff. The longer I use the terminal, the more of its power I come to respect. There's so many tools, so many parameters for each tool. It takes a really long time to build up muscle memory of what things you can do and remembering how to do them in that perfect situation.
Recently I've been trying to take at least 20 minutes a day to try and do things the tricky way by stringing these commands together. It's fun and the productivity wins of being able to string together several of these things in a pinch is fantastic.
Although it's definitely more fun than useful at this point~
Commands.dev is a curated, open-source collection of popular terminal commands that lets you quickly search for hard-to-remember terminal commands by title, tag, and description. Each of these pages are also indexed by Google to provide a consistent, well-formatted alternative to the variety of sources these commands turn up now, like StackOverflow.
As an engineer who uses the terminal frequently, I often have trouble remembering the exact command I want to execute if it’s not easily searchable within my terminal. Some commands that I run infrequently don’t match up with the underlying task they perform, which makes it even harder to find. For example, to undo my last git commit, I have to search for “git reset”, which I never remember because I’m always thinking “undo”ing my last commit instead of “reset”ing.
We built commands.dev so that there would be a centralized place to quickly find and search commands based on their name, description, or category. If you are a Warp user, these commands are also integrated directly into Warp as a feature we call Workflows (https://docs.warp.dev/features/workflows) so that you can quickly search and execute them directly from the terminal.
These commands are open-source (https://github.com/warpdotdev/workflows) and we would love contributions to make commands.dev even more useful. So far, we’ve already had 85 commands created by 22 unique contributors.
I’m excited to hear what you think of commands.dev! Our team sincerely hopes this will become a go-to tool on the Internet to consult when developers need to remember a difficult command, either directly on the site or by discovering a commands.dev page when searching Google for help with a command.
If you’re interested, join Warp’s Discord (www.warp.dev/discord) and follow us on Twitter (www.twitter.com/warpdotdev).
(I have a feeling that) my frequently used commands change depending on what I'm doing, and with time. Instead of trying to alias my current favourite commands, I tend to just use the backwards history search built in to my shell, and access it with Ctrl-R. I can type the beginning of the command and have the rest of it completed for me.
The only thing that would make it better is Ido-style completion.
reply