&gt;The suckless way is to have a short usage and a descriptive manpage. The complete details are in the source.<p>Can&#x27;t agree with that. Also this reminds me to the chapter about documentation in the &quot;UNIX Haters Guide&quot;[1]. (I recommend everyone read it for an alternative viewpoint about UNIX, although most of it is obsolete)<p>The GNU info system is actually a pretty good attempt to fix the mess that is classical UNIX documentation. No, the source shouldn&#x27;t be a documentation source. It&#x27;s for programmers only, and it can be a reference, like man pages. A good info page can provide a full manual from which someone that is not familiar with the program&#x2F;programming interface can learn how to proceed from scratch. Also, unlike man pages, info pages are hyperlinked. I agree that the info program itself is not very user friendly tho, maybe that&#x27;s the reason it&#x27;s not as popular as man pages or HTML documentation in the project website.<p>[1]: <a href="http:&#x2F;&#x2F;richard.esplins.org&#x2F;static&#x2F;downloads&#x2F;unix-haters-handbook.pdf" rel="nofollow">http:&#x2F;&#x2F;richard.esplins.org&#x2F;static&#x2F;downloads&#x2F;unix-haters-hand...</a>