News for hackers. Stuff that matters.
Re:Ask HN: Feedback on project by reidrac on Sunday August 07, 2011 @03:55PM (#2857566)
Cat is useless in that line:

   $ grep " 80/tcp" /etc/services 
   http            80/tcp          www www-http    # WorldWideWeb HTTP
http://partmaps.org/era/unix/award.html#cat
Re:Ask HN: Feedback on project by deno on Sunday August 07, 2011 @04:51PM (#2857682)
It's not useless. With cat, I don't have to remember the order of grep's arguments.
Re:Ask HN: Feedback on project by reidrac on Sunday August 07, 2011 @06:27PM (#2857972)
Interesting. With grep you need at least something to search (one argument), don't you? If you don't provide another argument to say "where", it reads from standard input (as most unix commands).

But you already know that because you're using it that way with cat. How can you don't remember then the order of the arguments?

Re:Ask HN: Feedback on project by deno on Monday August 08, 2011 @02:24AM (#2859040)
There:

> {1} With grep you need at least something to search (one argument), don't you? {2} If you don't provide another argument to say "where", it reads from standard input (as most unix commands).

And ‘find’ is the other way around.

I just don't see any reason to not to use cat. It's not like grep will use fseek() to speed anything up, if I call it with file URI instead.

Re:Ask HN: Feedback on project by iSloth on Sunday August 07, 2011 @05:12PM (#2857741)
I too would cat the file first, just get in the habit of doing it.