Hacker News Reader

The man page isn't too bad. It is better to just look at examples in my case and see what you can find.

I do agree it needs some work to be a little more approachable.

parallel --help is not friendly, and the man page is too comprehensive - really! - most of it belongs in /usr/share/doc

The examples are a pain to find - jump to the end (here comes the smack in the face) and see pages of differences to other tools.

It's a GNU project. It may have a texinfo manual from which the manpage is generated; if so, the info version will have hyperlinks and the like. (But you're probably better off reading the HTML version which should be, as you say, in /usr/share/doc.)

No one looks at texinfo docs.

pinfo is better than info for viewing info pages, but I agree: nobody looks at info pages. It's much easier to google documentation than to navigate to it in info.

I've been using Linux since about 1999 and have never looked at a texinfo page.

Or, at least, I don't think so, because I don't know what they are or how to access them.

The page with differences to other tools will be moved to 'man parallel_aternatives' in next version. It made sense when the section was short, but it has grown so big that it can make it harder to navigate.

Thanks for input.

(The trick to find the examples: LESS=+/EXAMPLE: man parallel )

Reply on news.ycombinator.com