7 ms·
Learn grep. If you're familiar with using a shell, it'll be the most immediately useful. # search current and all child directories for files containing "banan
by jibberia 12y ago
Learn grep. If you're familiar with using a shell, it'll be the most immediately useful.
# search current and all child directories for files containing "bananas", case insensitive
$ grep -ir "bananas" .
- scarecrowbob 12y agohere's an example of the first useful grep I learned : history | grep "git push"
- jpwgarrison 12y agoI alias "history | grep" to "hrep" and I'd bet it is one of my top 3-5 commands.
- spdustin 12y agoWhy not find out: history | awk '{a[$2]++}END{for(i in a){print a[i] " " i}}' | sort -rn | head
- scarecrowbob 12y ago:D HA! Nice! 2936 git 1166 cd 409 ll 343 ssh 302 l 279 vagrant 223 ls 201 la 151 cat 140 mkdir
- jakupovic 12y agouniq seems a bit easier to understand here: history | awk '{print $2}' | sort | uniq -c | sort -rn
- barrkel 12y agoWhy not use C-r?
- aaren 12y agoThis could change your life: https://github.com/junegunn/fzf https://github.com/junegunn/fzf It's a fuzzy searcher for Ctrl-r that shows all possible results, updating as you type.
- jpwgarrison 12y agoSometimes that is what I want, but usually I want a list of all the iterations of something to cut/paste/adjust.
- JetSpiegel 12y agoJust use Ctrl-R in bash to search backwards in the history
- scarecrowbob 12y agoI didn't know you could do that, so it's good to have an option- thanks. But how do you then pipe that to tail? :D
- JetSpiegel 12y agoYou don't, it's a readline thing, it doesn't really generate a file you can manipulate. (I expect to be proven wrong with some insane one-liner though). What you can do is press Ctrl-R again and it will search the older match. There's also forward match but I can't recall the shortcut.