this post was submitted on 26 Jan 2025
863 points (96.6% liked)

linuxmemes

22069 readers
1783 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     

    Clarification: Just making fun of people(including myself) who watch shitty videos instead of official documentation.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] tdawg@lemmy.world 76 points 1 day ago* (last edited 1 day ago) (5 children)

    Man pages are literally indecipherable as a newby

    [–] lightnsfw@reddthat.com 49 points 1 day ago (4 children)

    I just wish they'd put some damn usage examples in there. I usually just need to do one thing I don't need a dissertation about it.

    [–] someacnt@sh.itjust.works 1 points 16 hours ago

    As a CS bachelor, I feel like programmers are not so good at giving examples. They are used to refactoring to cover more general cases. It's a part that makes me struggle at mathematics the most, because good examples are like half of math.

    [–] Abnorc@lemm.ee 25 points 1 day ago (1 children)

    Some man pages have them. I agree that they should be more common though.

    [–] lurch@sh.itjust.works 12 points 1 day ago (1 children)
    [–] lightnsfw@reddthat.com 5 points 1 day ago

    I would say sometimes rather than usually.

    [–] superkret@feddit.org 13 points 1 day ago* (last edited 1 day ago)

    Install tealdeer. Then instead of man programname type tldr programname.

    [–] trucy@lemmy.dbzer0.com 1 points 1 day ago (1 children)

    manpages of gnu commands usually lack them because they're in their info system

    [–] QuazarOmega@lemy.lol 4 points 1 day ago (1 children)
    [–] furikuri@programming.dev 7 points 1 day ago

    Run info info

    Texinfo pages were originally meant to be a longer alternative to manpages that had support for featureful navigation (links, indexes, etc). They're nice and I can see a world where they did catch on, but the standard viewer is always a little bit of a shock to jump in to (being based off Emacs and all)

    [–] sundrei@lemmy.sdf.org 15 points 1 day ago

    No worries!

    man man

    ... I'm in over my head here.

    cht () {
        curl cht.sh/$1
    }
    

    You can stick this in your .bashrc or .bash_profile. Then just do cht <command to use> and it'll give you the most relevant info to use the command.

    Ie. cht tar

    [–] ImplyingImplications@lemmy.ca 5 points 1 day ago (2 children)

    Here's a excerpt from man chmod that can be summarized as "You probably want to mark the file you downloaded as executable. Run chmod +x FILENAME"

    DESCRIPTION
    This manual page documents the GNU version of chmod. chmod changes the file mode bits of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new mode bits.

    The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo. Multiple symbolic modes can be given, separated by commas.

    A combination of the letters ugoa controls which users' access to the file will be changed: the user who owns it (u), other users in the file's group (g), other users not in the file's group (o), or all users (a). If none of these are given, the effect is as if (a) were given, but bits that are set in the umask are not affected.

    The operator + causes the selected file mode bits to be added to the existing file mode bits of each file; - causes them to be removed; and = causes them to be added and causes unmentioned bits to be removed except that a directory's unmentioned set user and group ID bits are not affected.

    The letters rwxXst select file mode bits for the affected users: read (r), write (w), execute (or search for directories) (x), execute/search only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), restricted deletion flag or sticky bit (t). Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o).

    A numeric mode is from one to four octal digits (0-7), derived by adding up the bits with values 4, 2, and 1. Omitted digits are assumed to be leading zeros. The first digit selects the set user ID (4) and set group ID (2) and restricted deletion or sticky (1) attributes. The second digit selects permissions for the user who owns the file: read (4), write (2), and execute (1); the third selects permissions for other users in the file's group, with the same values; and the fourth for other users not in the file's group, with the same values.

    chmod doesn't change the permissions of symbolic links; the chmod system call cannot change their permissions on most systems, and most systems ignore permissions of symbolic links. However, for each symbolic link listed on the command line, chmod changes the permissions of the pointed-to file. In contrast, chmod ignores symbolic links encountered during recursive directory traversals. Options that modify this behavior are described in the OPTIONS section.

    [–] Whateley@lemm.ee 1 points 4 hours ago

    Yes, but can I dance to it?

    [–] tdawg@lemmy.world 4 points 1 day ago

    This is a perfect example bc five years ago this would be total gibberish to my fledgling self. But today it's mostly readable as reference material

    [–] Jumuta@sh.itjust.works 4 points 1 day ago

    this is why tldr is so good