this post was submitted on 20 Apr 2024
563 points (90.9% liked)

linuxmemes

21189 readers
300 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 members of the community for any reason.
  • 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, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 22 points 6 months ago (3 children)

    not seen in this comic: the linux file isn't where the comic/manual/internet nerds says it should be, and there's no realistic way to find it

    [–] [email protected] 3 points 6 months ago (1 children)

    Sure there is: find / -name myprogram*.md -o -name myprogram*.txt or start with just looking for the program name and pipe to less

    [–] [email protected] 8 points 6 months ago (1 children)
    [–] [email protected] 5 points 6 months ago

    The prompt was realistic not simple lol. Usually some man or programname -h and then reading will tell you where to look and that's simple. Not many people want to hear "RTFM" though.

    [–] [email protected] 1 points 6 months ago* (last edited 6 months ago)

    Until flatpak came along and just keeps everything in their respective app sandbox.

    If your app don't need full user home access (most app don't), you can use a persistent folder to place the folder in app sandbox instead of home.

    It is not only more clean, but also more secure and private.

    [–] [email protected] -1 points 6 months ago (1 children)

    Nonsense. And even if the config file cannot be found in the usual directories then there are always tools like KFind that can search your entire OS within seconds.

    [–] [email protected] 10 points 6 months ago (2 children)

    congratulations. you've just sent a linux newb down a 12 hour rabbit hole that doesn't actually solve their problem.

    [–] [email protected] 13 points 6 months ago

    and thats the power of linux baby hell yeah

    [–] [email protected] 2 points 6 months ago

    How does it not solve their problem if they're searching for configuration files? That would only be the case if the files do not exist in the first place, and then there's really no difference between GNU/Linux and Windows at all if you assume that initial configuration has not occurred. What would you do?