Chris

But that is the right way to handle this

because it is correct to give pointers like
read grep
or something like that
but writing a whole script is a no-no



On Mon, Apr 5, 2010 at 11:46 AM, Chris Miller
<[email protected]>wrote:

> On Mon, Apr 5, 2010 at 5:54 AM, Robert Citek <[email protected]>
> wrote:
> > On Sun, Apr 4, 2010 at 11:42 PM, Chris Miller
> > <[email protected]> wrote:
> >> Don't give thanks in advance:
> >>
> >>    
> >> http://www.catb.org/~esr/faqs/smart-questions.html#courtesy<http://www.catb.org/%7Eesr/faqs/smart-questions.html#courtesy>
> >
> > That's not quite what is written:
> >
> > <quote>
> > Some hackers feel this connotes an intention not to thank anybody
> > afterwards. Our recommendation is to either say “Thanks in advance”
> > first and thank respondents afterwards, or express courtesy in a
> > different way, such as by saying “Thanks for your attention” or
> > “Thanks for your consideration”.)
> > </quote>
> >
> > Note "Some hackers", not all.  "Some hackers" are socially maladroit
> > and gauche.  "Some" don't bathe.  So, one might want to take their
> > social advice about courtesy with a hefty grain of salt (or Purell).
>
> I made that snippet as a canned response a year or so ago.  I think it
> changed in that time.
>
> Just me and my collection of stale links, nothing to see here.  Move along.
>  :)
>
> On Mon, Apr 5, 2010 at 9:00 AM,  <[email protected]> wrote:
> > It's the shorthand way of saying "Get outta here, kid".
> >
> > It actually means "Read the freaking manual", meaning that the answers
> > sought can be found in the program's general documentation. Since it's
> > considered good etiquette  to make a good faith effort to find your own
> > answers before asking a user's group, many hackers feel self righteous
> > and say 'RTFM' whenever the answer is already documented someplace.
> >
> > While this attitude may be fitting on occasion, I think it's generally
> > more inflammatory than helpful. Pointing the user to the documentation
> > (maybe with a quick note on how you found the answer) is more
> > constructive.
>
> If you're new to shell scripting it isn't obvious.  There's nothing
> about the name "grep" which (to me) says "find stuff in text."
>
> So I basically tossed a few command names at you and now I expect you
> to make use of documentation to figure out how to pass them the
> correct arguments, etc. to create the proper script (and toss that in
> cron or what have you).
>
> So I guess mine was kind of more like "Read THIS Freaking Manual" than
> anything else.
>
> The OP smelled rather like a homework question though, which triggered
> my intensely primal snobbery.
>
> --
> Registered Linux Addict #431495
> For Faith and Family! | John 3:16!
> http://www.fsdev.net/
>
> --
> You received this message because you are subscribed to the Linux Users
> Group.
> To post a message, send email to [email protected]
> To unsubscribe, send email to [email protected]
> For more options, visit our group at
> http://groups.google.com/group/linuxusersgroup
>
> To unsubscribe, reply using "remove me" as the subject.
>

-- 
You received this message because you are subscribed to the Linux Users Group.
To post a message, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit our group at 
http://groups.google.com/group/linuxusersgroup

Reply via email to