Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 09-May-2024 07:25:07 JST Haelwenn /элвэн/ :triskell:

   • Piggo :verified_horse:
   • LEdoian

   @ledoian @piggo Which isn't surprising given that the paste(1) and join(1) manpages from GNU are horribly incomplete.
   Which is yet another reason why I have man-pages-posix on most of my client machines, see https://manned.org/join.1p and https://manned.org/paste.1p for example.

   But looking at it again, I think rsync(1) manpage is pretty good, even provides some examples right from the start.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 09-May-2024 09:04:43 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Piggo :verified_horse:
     • LEdoian
     @ledoian @piggo Yeah, reminds me that the reason why my software targets POSIX make(1) with a bit of BSD-style extensions (And all the ones I use are in POSIX drafts) is because I can actually read the documentation of those painlessly and it works with GNU Make as well anyway.
   • Embed this notice
     LEdoian (ledoian@pleroma.ledoian.cz)'s status on Thursday, 09-May-2024 09:04:45 JST LEdoian

     in reply to

     • Piggo :verified_horse:

     @lanodan @piggo Whenever I use manpages, I use man -a and quickly skip from GNU pages to the POSIX ones. (For section 1, that is; OTOH system APIs often read better from Linux man-pages than from POSIX.)

     I quite hate how GNU manpages mostly give the incantation for the actual documentation (Full documentation […] available locally via: info '(coreutils) ls invocation'). And for stuff like make(1), GNU manpage is pretty much a complete joke (lists only flags for the command, not the language).

     But still for common invocations, I find tldr is usually quicker than the manpage.