News for hackers. Stuff that matters.
Re:Sed – An Introduction and Tutorial by jpwgarrison on Wednesday January 07, 2015 @11:42PM (#8855033)
I alias "history | grep" to "hrep" and I'd bet it is one of my top 3-5 commands.
Re:Sed – An Introduction and Tutorial by spdustin on Thursday January 08, 2015 @12:47AM (#8855163)
Why not find out:

  history | awk '{a[$2]++}END{for(i in a){print a[i] " " i}}' | sort -rn | head
Re:Sed – An Introduction and Tutorial by jakupovic on Thursday January 08, 2015 @10:27AM (#8856752)
uniq seems a bit easier to understand here:

history | awk '{print $2}' | sort | uniq -c | sort -rn

Re:Sed – An Introduction and Tutorial by scarecrowbob on Thursday January 08, 2015 @01:08AM (#8855204)
:D HA! Nice!

2936 git 1166 cd 409 ll 343 ssh 302 l 279 vagrant 223 ls 201 la 151 cat 140 mkdir

Re:Sed – An Introduction and Tutorial by barrkel on Thursday January 08, 2015 @05:12AM (#8855760)
Why not use C-r?
Re:Sed – An Introduction and Tutorial by aaren on Thursday January 08, 2015 @10:43AM (#8856834)
This could change your life:

https://github.com/junegunn/fzf

It's a fuzzy searcher for Ctrl-r that shows all possible results, updating as you type.

Re:Sed – An Introduction and Tutorial by jpwgarrison on Thursday January 08, 2015 @12:25PM (#8857474)
Sometimes that is what I want, but usually I want a list of all the iterations of something to cut/paste/adjust.