It seems I’m a ruby guy after all:
$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -rn | head -10
111 svn
61 cd
44 rake
36 l
32 hg
18 ./script/console
14 rm
12 screen
12 history
12 ./script/server
It seems I’m a ruby guy after all:
$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -rn | head -10
111 svn
61 cd
44 rake
36 l
32 hg
18 ./script/console
14 rm
12 screen
12 history
12 ./script/server
Nifty! Here’s mine:
153 sudo
62 cd
48 ls
25 ping
20 rm
16 ifconfig
13 vim
12 pkill
11 exit
9 glxgears
wow, big fan of glxgears
Hmm, never thought about checking these stats before, here’s mine:
104 cd
99 ls
63 svn
48 ./script/console
41 kate
27 less
22 rake
11 ri
11 irb
10 vi
I guess “grep” is really underrepresented, usually being on the tail-end of one of the above commands, and I was pretty sure I used “find” more often than that.
I’ll blame the Rails directory structure for the dominance of cd and ls.
I guess i’m a network guy.
44 ls
43 cd
33 sudo
22 clear
20 ssh
13 scp
11 vi
10 ps
7 ifconfig
7 exit
jajajaja… what you been doing Mike? Nice Rake Kate
btw, I would add grep -v history, so history doesn’t show, cause obviously, it’s used only for this purpose now and not as a common every day command.
herman@ts:~$ history | awk ‘{print $2}’ | awk ‘BEGIN {FS=”|”} {print $1}’|sort|uniq -c | sort -rn | head -10
258 ssh
41 ls
33 exit
22 cd
17 apt-cache
15 killall
12 sudo
11 vim
9 scp
8 man
Herman, that’s a lot of exits. Have you tried using Control-D?
nice!
66 cd
60 ll
51 ps
26 pp
24 sudo
23 kill
22 vi
15 su
13 q
12 ping
where
pp=”ping [mywebsite]”
q=”exit”
$ history | awk ‘{print $2}’ | awk ‘BEGIN {FS=”|”} {print $1}’|sort|uniq -c | sort -rn | head -10
64 cat
54 ssh
51 cd
40 ls
27 vim
26 sudo
22 clear
20 mv
19 echo
16 less