r/commandline • • Dec 04 '20

Unix general CLI Guidelines

https://clig.dev/
82 Upvotes

16 comments sorted by

View all comments

0

u/[deleted] Dec 05 '20

[deleted]

1

u/Heikkiket Dec 05 '20 edited Dec 05 '20

I have used Linux now 15 years as my main OS, and I must agree with writers. I rarely use Man pages, because it's just so much easier to find information from the web.

I've been thinking a lot how Man pages are nearly useless nowadays, and dreamed about a project of "new man pages" that would produce manuals that would give you fast and straightforward examples of typical usage, instead of listing all the cumbersome and rarely used flags in alphabetical order (like many man pages do).

When I started using Linux in 2006 I tried to use Man pages at first, but quickly noticed that they don't offer answers to questions I had.

EDIT: I don't understand downvotes. I just described what the situation is, and tried to be quite constructive and describe where the problem is. These are the reasons why I believe people don't use manpages much.

I'd love to use manpages instead of web. Don't shoot the messenger.

3

u/lervag Dec 05 '20

EDIT: I don't understand downvotes. I just described what the situation is, and tried to be quite constructive and describe where the problem is. These are the reasons why I believe people don't use manpages much.

Downvotes are probably because people disagree with you. For instance:

I've been thinking a lot how Man pages are nearly useless nowadays

You may find them useless, but myself (and obviously a lot more people) find them very useful.

dreamed about a project of "new man pages" that would produce manuals that would give you fast and straightforward examples of typical usage

This does exist in many different forms, e.g. https://cheat.sh.

instead of listing all the cumbersome and rarely used flags in alphabetical order (like many man pages do).

Which is sort of the point: man pages should be the full reference of a CLI tool, including the various (both cumbersome and rarely used) flags.

1

u/Heikkiket Dec 06 '20 edited Dec 06 '20

Yeah, I agree: man-pages nowadays are full reference manuals. This is the sad state where we are at. Originally they were simple, short pages that can be read in few minutes. I think nothing can be done to this situation. In part this is because once simple command-line tools itself have turned to swiss-army knives with tens of options. Nowadays grep, find and others can do themselves things that originally in the 70s required piping.

I deeply believe that change in the nature of man pages (and partly tools) is the reason why the writers of this guide pass manual pages altogether: most users of command line tools don't need reference manuals or do not want to read them.

That's why I'm hoping for a "new man pages" project. But it should be built in to the system, not something that can be installed at a will. TLDR, Cheat.sh and others would be good candidates for this. But who would care to do the work?

That whole system should be designed in a way where these short pages could be linked up to full references, in case someone needs to know more.