6 ms·

Whut? ctrl-r? How have I missed that? No more 'history|grep foo' for me!

btipling 14y ago
Also ag is faster and better than grep: https://github.com/ggreer/the_silver_searcher https://github.com/ggreer/the_silver_searcher
pavel_lishin 14y ago
Try this in your .inputrc: # Bind the up arrow to history search, instead of history step "\e[A": history-search-backward "\e[B": history-search-forward No more "^rls" to search for ls in your bash history; just type "ls" and start hitting the up arrow.
- dunk010 14y ago
  This is the best tip ever.
- nathanstitt 14y ago
  Thanks for the suggestion. I used to have a very customized .bashrc with nice little things like that, but have decided to stick with standard stuff for things that work off of muscle memory. I got tired of sshing into a new box and half the things I'd type wouldn't work properly until I remembered to copy my settings files over, which seemed more trouble than it was worth for a short-lived s3 instance. That's why I was excited to discover ctrl-r. It's a built-in method of searching history that I can remember and it'll work everywhere.
  - pavel_lishin 14y ago
    > I got tired of sshing into a new box ... I've got a public repo of my dotfiles, so the first thing I typically do is "git clone git@github.com:pavellishin/dotfiles.git && cd dotfiles && ./install.sh" After that, I launch tmux, and it's all hunky dory.
    - nathanstitt 14y ago
      Heh.. right after I posted that comment, my thought was: 'you know - the correct answer here would have been to make an Uber command that would suck all the configs in and install them'. Thanks for giving me the push to do so. I think I'll take your suggestion but put the command on a site somewhere so I can simply 'curl https://foo.bar/configs https://foo.bar/configs | bash'
lucastheisen 14y ago
If you are using 'set -o vi', then you can just use 'ESC' -> '/<somePartOfCommand>' then use 'n' to iterate in reverse order through the commands that match the vi regex. really powerful and useful.

Also ag is faster and better than grep: https://github.com/ggreer/the_silver_searcher https://github.com/ggreer/the_silver_searcher

pavel_lishin 14y ago

Try this in your .inputrc: # Bind the up arrow to history search, instead of history step "\e[A": history-search-backward "\e[B": history-search-forward No more "^rls" to search for ls in your bash history; just type "ls" and start hitting the up arrow.

dunk010 14y ago
This is the best tip ever.
nathanstitt 14y ago
Thanks for the suggestion. I used to have a very customized .bashrc with nice little things like that, but have decided to stick with standard stuff for things that work off of muscle memory. I got tired of sshing into a new box and half the things I'd type wouldn't work properly until I remembered to copy my settings files over, which seemed more trouble than it was worth for a short-lived s3 instance. That's why I was excited to discover ctrl-r. It's a built-in method of searching history that I can remember and it'll work everywhere.
- pavel_lishin 14y ago
  > I got tired of sshing into a new box ... I've got a public repo of my dotfiles, so the first thing I typically do is "git clone git@github.com:pavellishin/dotfiles.git && cd dotfiles && ./install.sh" After that, I launch tmux, and it's all hunky dory.
  - nathanstitt 14y ago
    Heh.. right after I posted that comment, my thought was: 'you know - the correct answer here would have been to make an Uber command that would suck all the configs in and install them'. Thanks for giving me the push to do so. I think I'll take your suggestion but put the command on a site somewhere so I can simply 'curl https://foo.bar/configs https://foo.bar/configs | bash'

lucastheisen 14y ago

If you are using 'set -o vi', then you can just use 'ESC' -> '/<somePartOfCommand>' then use 'n' to iterate in reverse order through the commands that match the vi regex. really powerful and useful.