I try to remember commands backwards by how they look(<command> <flags> <arguments>), if they are short, have capital letters and so on… Is that weird? If I give up I open the history file or my good ol’ cheat sheet.
I did use it but the only real benefit for me as a hobbyist was the git status indicator on the prompt and the easy to configure prompt. The rest of the indicators did not help me since I’m not a developer. Now I just have my custom prompt with colors, and custom git info.
I quite sure fish has it, but I use zsh without autocompletions, I just press tab until I find what I need. And the fzf history shortcuts for the rest.
Fish does history autocomplete, not Starship — you still have autocomplete using unconfigured Fish, and you don’t get autocompletion by enabling Starship for other shells.
I try to remember commands backwards by how they look(<command> <flags> <arguments>), if they are short, have capital letters and so on… Is that weird? If I give up I open the history file or my good ol’ cheat sheet.
(Tip: Most shells allow you to press Ctrl+R to interactively search through history, meaning you won’t have to open a separate file.)
Oh. My. Word.
I thought I was clever by using
history | grep <bit of command I remember>I KNEW there had to be a better way!
You need https://starship.rs/
I did use it but the only real benefit for me as a hobbyist was the git status indicator on the prompt and the easy to configure prompt. The rest of the indicators did not help me since I’m not a developer. Now I just have my custom prompt with colors, and custom git info.
But it autocompletes pretty well, isn’t it? 🤔or was it fish doing that
I quite sure fish has it, but I use zsh without autocompletions, I just press tab until I find what I need. And the fzf history shortcuts for the rest.
Fish does history autocomplete, not Starship — you still have autocomplete using unconfigured Fish, and you don’t get autocompletion by enabling Starship for other shells.