Re: let's beef up the tsort info page

[Kenny McCormack]

In article <address@hidden>,
Dan Jacobson <address@hidden> wrote:
>Fellas, I think to explain tsort to the widest number of users, you
>would need one or two pages of pure user/shell interaction, with no
>attempt at English explanation until maybe the very end.
>
>For some reason the command line interaction stuff seems to soak in
>[to my head] while the English explanation attempt kind of just floats
>on the surface.

First of all, I'd never heard of tsort before seeing this thread.  Having
read the thread and checking the man page on my system, it looks kinda
interesting, although I'd be curious to know where it came from (and why!).

That said, I think what the other posters in this thread are saying is that
if you don't know what the command does, you should just ignore it.  It is
an attitude common on Usenet and in the computer world in general - and,
quite frankly, it makes sense in most cases.  But it does make it
frustrating when you've just stumbled onto a neat little Unix command and
want to know what it does.

Finally, note that the tsort man page on my system (RH Linux) seems to put
a considerably different slant on things than does the text quoted so far.
It talks about "directed graphs" and "nodes" and such.  Not only that, but
in the "see other" section, it mentions "ar" (which, as we all know, is
part of the compiler toolchain...)