• SpicySquid@lemmy.ml
    link
    fedilink
    arrow-up
    50
    ·
    8 months ago

    Well… I guess I have been living under a rock. Today is the first time to have heard of info. I have been using man for well over 2 decades now.

    • palordrolap@kbin.social
      link
      fedilink
      arrow-up
      10
      ·
      8 months ago

      Surprising you haven’t come across a man page that basically says “We couldn’t be bothered putting everything in here, check out the info page on it instead.”

      I feel like I find myself on one of those every 6 months or so.

      • BaumGeist@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        8 months ago

        That’s funny, I had the opposite experience. When I found out that info was the GNU projects recommended way of documentation, I was all on board. Then I tried using it, and it couldn’t find most CLI software I used. So I downloaded the texinfo archives… and that still lacked probably 50% of the commands I tried to look up.

        Then I searched up how to get info pages for this or that tool, and someone on StackOverflow had said that it was woefully incomplete and outdated at this point.

        I think I’ll give it another try and report back

  • iusearchbtw@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    12
    ·
    9 months ago

    man is standard Unix manual pages, while info is a documentation format introduced/popularised by GNU. info pages usually have a lot more information (sometimes including tutorials, guided examples, links to different pages and sections, etc (depending on the project maintainer obviously)) but man pages are the standard and basically everything has one. If you run info [program] for something without a dedicated info page, it will show the man page instead.

  • macallik@kbin.social
    link
    fedilink
    arrow-up
    10
    ·
    8 months ago

    My impression
    tldr/cheat: Explains most popular arguments using as little words as possible
    man: Explains the entire command using a more technical tone
    info: Explains the entire command in slightly more informal tone. Can feel wordier as a result, but on the flipside it connects alternative/related commands in a logical way

    • folkrav@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      8 months ago

      I since switched to tldr (for the offline/caching functionality, I think?), but for the longest time I just used a wrapper function that did exactly this in my shell configuration. Something a bit like this:

      function cheatsh() { 
          curl cheat.sh/"\$1" 
      }