<div>Oh. I've used that many times as well. Like to make a Top Ten list of the most popular things:</div>
<div><strong><em>something</em> | sort | uniq -c | sort -nr | head</strong><br><br> </div>
<div><span class="gmail_quote">On 12/23/05, <b class="gmail_sendername">Luke-Jr</b> <<a href="mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Friday 23 December 2005 15:23, Monty J. Harder wrote:<br>> On 12/22/05, Luke-Jr <<a href="mailto:luke@dashjr.org">
luke@dashjr.org</a>> wrote:<br>> > On Friday 23 December 2005 04:35, Jim Herrmann wrote:<br>> > > Thanks to Ron also. This may be easier to remember since it uses more<br>> > > common commands.
<br>> ><br>> > How is 'sort' and more common than 'uniq'? I really only use the two in<br>> > combination (uniq -c | sort -n) anyway...<br>><br>> That's backwards. You have to put the *sort* to the left of the *uniq* for
<br>> it to work, because *uniq* requires that its input already be sorted. The<br>> beauty of the Unix philosophy is that *uniq* doesn't have to know about<br>> sorting, because *sort* already does.<br><br>Not quite backwards, read it again-- you're right that it does require
<br>presorted content, though.<br></blockquote></div><br>