Look, I'm lazy, okay?
Look, I'm lazy, okay?
Comments
86-
-
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)
-
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!
-
-
Also works in fish
-
But how to go backwards and forwards through the results? I just cycle through again!!
-
As @wandering_nomad@lemmy.world said above, Ctrl+S
-
-
Wish I knew this sooner.
-
-
-
This is my approach, and for those who don't know, you can use those line numbers that come back from
historyto rerun the command. Like if your output is something like this:$ history | grep tmp 501 ls /tmp 502 history | grep tmpYou can run
!501and it will just re-runls /tmp-
Woah! I had no clue!
-
-
I got that as
hgrep -
-
Yall are missing out on autocomplete.
-
-
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.
-
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.
-
-
fzf masterrace
-
up, up, up, up, up, cd .., ah there it is.
-
⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬇️ ⬇️
-
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. -
It's even faster if you look for it inside .bashhistory.
-
Still noup
-
-
Using the history command just to find the specific IP I need to ssh to
-
More like to find ping -O 8.8.8.8
-
-
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
-
-
Same. Look at all these people using grep to search their history.
-
-
We will history | grep docker until morale improves
-
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.
-
-
history | grep {search term}
-
"python3 -m http.server"
-
This is the way!
-
I just use the 'fuck' command after lazily typing letters that somewhat match the command I want to run
-
https://github.com/marlonrichert/zsh-autocomplete Autocomplete for Zsh
-
Yeah but last time I typed it, it worked. Who knows what ridiculous typos I'd make right now?
-
I’ve always used set -o vi. Let’s you use vi commands on the bash prompt.
-
I just manage to forget what to type and I'm too lazy to look it up. that and I'm lazy
-
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.
-
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.
-
-
-
It's not about the keystrokes. It's the principle!
-
Oh shit I definitely do this XD
-
I feel seen.
-
poweroff
-
Lol stop attacking me! 😭
-
Ctrl + R to search in command history 👍.
-
old habits die hard autocomplete for your shell is so clutch though
-
i use vi mode in zsh for that reason, its pretty good
-
up up up up up up up up oh wait down
control shift R, then start typing, it will search your bash history
Is it not just Ctrl-R or is that platform dependent
I have always used ctrl-r but I just checked and both work. TIL.
Hmm, normally it's just ctrl - r... Are you sure the shift is needed on your system?
Don't forget fzf. That will really jazz up your history search!
you are right, I must have just learned it with a shift for some dumb reason and it stuck, thank you internet person.
Some variants have ctrl+r bound to something else
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!
I recommend using mcfly for that, it makes it even better.
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?
Why r? Maybe if I knew why r, then I wouldn't forget this every 13 seconds...
Reverse search