https://github.com/junegunn/fzf
I recommend installing it as an oh-my-zsh plugin, but it's not hard to get running in vanilla zsh/bash
Ok if you want to learn Linux, you need to start web searching for stuff you hear about. :)
you are right, I must have just learned it with a shift for some dumb reason and it stuck, thank you internet person.
Now if you had to guess how often I remember that there is a keyboard shortcut that does this, but don't remember what it is, and do remember that I can just press up 30-70 times...
you can hit it again after you are dialed in as much as you want and it will keep going back in time with the words you have in there and stuff that matches!
CTRL+R brings up a prompt and allows you to search through commands you’ve run before. If you’ve run different variations of the command hitting CTRL+R or CTRL+SHIFT+R cycles through commands similar to what you’ve typed out.
I'm new to linux and i've been using $history | grep <thingy>. This information is very useful, thank you.
Sure thing! There’s lots of ways to do the same things, but either way stops you from hitting the up key a bajillion times
Ctrl+R
Then type any part of the command (filename, search string, etc)
Ctrl+R again to cycle through the matches.
(Best feature in bash)
But how to go backwards and forwards through the results? I just cycle through again!!
This is my approach, and for those who don't know, you can use those line numbers that come back from history to rerun the command. Like if your output is something like this:
$ history | grep tmp
501 ls /tmp
502 history | grep tmp
You can run !501 and it will just re-run ls /tmp
didn't know there was a comment for that, I just always used cat to read the bash history file
Wait until you learn about ctrl-R to search the bash history... :) If you press that and start typing, you will get auto complete from previous commands you typed. This is how an experienced linux user can be so fast in the terminal.
There are even better tools for this, so ctrl R is just the built in way. Later you should look into https://github.com/junegunn/fzf
This is why I switched to fish; it seems to be much smarter understanding what I want to type.
Yeah it's great how ctrl-r is kinda the default instead of something you have to go out of your way to use. Just start typing a command and the up arrow will only cycle through history that matches what you've typed so far.
Idk exactly what plugin it is, but zsh + oh my zsh has exactly this same thing. So hard to live without now that I'm used to it. Probably my favorite feature
Yeah it's great how ctrl-r is kinda the default instead of something you have to go out of your way to use. Just start typing a command and the up arrow will only cycle through history that matches what you've typed so far.
Yeah it's great how ctrl-r is kinda the default instead of something you have to go out of your way to use. Just start typing a command and the up arrow will only cycle through history that matches what you've typed so far.
It's like the bus-stop-paradigm: If I wait just a bit longer and it will come. Meanwhile it would've been faster to walk.
To anyone who uses vim mode, ? lets you search through your stored command history, from normal mode ofc.
I create so many aliases with the notion of how much time I’ll save… never use ‘em. Works out okay though because a much richer history to fzf through
Gah it's all docker container ps -a. OK, fine, history | grep "docker run".
Next time I'll put a file in the project directory that tells me how I ran it and .gitignore it. I promise. Next time.
I just use the 'fuck' command after lazily typing letters that somewhat match the command I want to run