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)
this post was submitted on 04 Jul 2023
135 points (100.0% liked)
linuxmemes
20747 readers
674 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Or history | grep 'command'
Can't just hit enter to run the one you want then, though.
Type: !1234 ... to run whatever history number of the command.
Use fzf for a more visual search.
This is the way.
I've been using this for a long time, never knew I could press Ctrl + R again. Thanks!
Ctrl + S to go the other way if you overshoot!
control shift R, then start typing, it will search your bash history
This. It took a while for it to sink in but now it’s muscle memory and a huge time saver
What now? What is r? How does this work?
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 . 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
Hmm, normally it's just ctrl - r... Are you sure the shift is needed on your system?
Some variants have ctrl+r bound to something else
Don't forget fzf. That will really jazz up your history search!
No man entry for fzf
Ok if you want to learn Linux, you need to start web searching for stuff you hear about. :)
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.
up, up, up, up, up, cd .., ah there it is.
history | grep 'command'
I use this all the time. Even better if you add it as a function.
⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬇️ ⬇️
Using the history command just to find the specific IP I need to ssh to
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.
Tfw I rather type it out instead of searching through the history
I use xonsh, which has decent history - start your command, and up arrow cycles through commands stating with what you typed.
There's good stuff and bad stuff about xonsh.
view more: next ›