> But is it really all used? I have never heard of searching man pages by e.g. return type (in section 2 or 3 I assume this would be) For example, here’s a sea

> But is it really all used? I have never heard of searching man pages by e.g. return type (in section 2 or 3 I assume this would be) For example, here’s a search for “functions beginning with ‘str’ and with return type size_t”: http://www.openbsd.org/cgi-bin/man.cgi?query=Ft%3Dsize_t+-a+Fn~^str&sec=3&apropos=1 http://www.openbsd.org/cgi-bin/man.cgi?query=Ft%3Dsize_t+-a+... On OpenBSD you can do the same from a terminal: $ apropos -s 3 Ft=size_t -a Nm~^str As for hyperlinks, this of course depends on your output format. less(1) in a terminal doesn’t do hyperlinks. HTML output will, such as in this page: http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/afterboot.8 http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/... And a distribution could, for example, configure man(1) to trigger Lynx (or even Firefox) looking at Mandoc’s HTML output. These toolchains are still being actively developed and improved (semantic search, for example, has only been around for a couple years despite the format theoretically supporting it since the beginning). I try to do my part by contributing manpages to projects that don’t have one, converting to mdoc macros when practical, and explaining the great featureset available. The best part is that it is so widely supported—at worst, mdoc falls back to the manpage infrastructure we have now; deployment of a new toolsuite is not a problem compared to converting to some brand new format. At best, it supports all these great new features, and it does so today!