1 yr. ago • 98%

Look, I'm lazy, okay?

85 comments

control shift R, then start typing, it will search your bash history

54
- Is it not just Ctrl-R or is that platform dependent
  
  15
  
  I have always used ctrl-r but I just checked and both work. TIL.
  
  6
- Hmm, normally it's just ctrl - r... Are you sure the shift is needed on your system?
  
  12
  
  Don't forget fzf. That will really jazz up your history search!
  
  3
  
  you are right, I must have just learned it with a shift for some dumb reason and it stuck, thank you internet person.
  
  2
  
  Some variants have ctrl+r bound to something else
  
  1
- 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...
  
  7
  
  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!
  
  3
- I recommend using mcfly for that, it makes it even better.
  
  6
- This. It took a while for it to sink in but now it’s muscle memory and a huge time saver
  
  4
  
  What now? What is r? How does this work?
  
  3
- Why r? Maybe if I knew why r, then I wouldn't forget this every 13 seconds...
  
  3
  
  Reverse search
  
  10
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)

49
- Use fzf for a more visual search.
  
  12
  
  This is the way.
  
  5
- I've been using this for a long time, never knew I could press Ctrl + R again. Thanks!
  
  8
  
  Ctrl + S to go the other way if you overshoot!
  
  8
- Or history | grep 'command'
  
  6
  
  Can't just hit enter to run the one you want then, though.
  
  3
- Wish I knew this sooner.
  
  1
- But how to go backwards and forwards through the results? I just cycle through again!!
  
  1
  
  As @wandering_nomad@lemmy.world said above, Ctrl+S
  
  1
history | grep 'command'

I use this all the time. Even better if you add it as a function.

12
- 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
  
  7
  
  Woah! I had no clue!
  
  1
- I got that as hgrep
  
  6
  
  Mine is hists for 'history search'. Interesting how we came up with different names for the same thing.
  
  2
- Yall are missing out on autocomplete.
  
  6
  
  I love autocomplete, use it all the time.
  
  2
- didn't know there was a comment for that, I just always used cat to read the bash history file
  
  3
  
  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
  
  2
  
  grep is sooo useful. Combined with piping commands it can do some really powerful stuff. I didn't really understand a lot of these commands until I took a Linux class at my local community college. That helped a lot.
  
  1
Permanently Deleted

11
up, up, up, up, up, cd .., ah there it is.

10
fzf masterrace

10
This is why I switched to fish; it seems to be much smarter understanding what I want to type.

9
- 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.
  
  7
  
  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
  
  2
- 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.
  
  0
- 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.
  
  0
⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬇️ ⬇️

9
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.

8
It's even faster if you look for it inside .bash_history.

7
- Still noup
  
  2
Using the history command just to find the specific IP I need to ssh to

7
- More like to find ping -O 8.8.8.8
  
  1
To anyone who uses vim mode, ? lets you search through your stored command history, from normal mode ofc.

7
Permanently Deleted

6
- Same. Look at all these people using grep to search their history.
  
  2
We will history | grep docker until morale improves

5
- 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.
  
  4
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

5
https://github.com/junegunn/fzf

5
I just use the 'fuck' command after lazily typing letters that somewhat match the command I want to run

4
history | grep {search term}

4
"python3 -m http.server"

4
This is the way!

4
I’ve always used set -o vi. Let’s you use vi commands on the bash prompt.

3
https://github.com/marlonrichert/zsh-autocomplete Autocomplete for Zsh

3
Yeah but last time I typed it, it worked. Who knows what ridiculous typos I'd make right now?

3
It's not about the keystrokes. It's the principle!

2
I just manage to forget what to type and I'm too lazy to look it up. that and I'm lazy

2
Oh shit I definitely do this XD

2
Tfw I rather type it out instead of searching through the history

2
- 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.
  
  1
  
  I rarely use fuzzy finder to search up the commands that I'm going to use. If you realise that a certain command with arguments is often being used, you should create an alias for it so that you don't have need that memory load. That being said, I appreciate shell like fish provides auto complete (derived from command history) to speed up my workload.
  
  1
i use vi mode in zsh for that reason, its pretty good

1
Lol stop attacking me! 😭

1
Ctrl + R to search in command history 👍.

1
old habits die hard autocomplete for your shell is so clutch though

1
poweroff

1
I feel seen.

1
up up up up up up up up oh wait down

0

You've viewed 85 comments.