this post was submitted on 09 Jul 2023
1246 points (97.2% liked)

linuxmemes

21263 readers
513 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
    [โ€“] MellowSnow@lemmy.world 7 points 1 year ago* (last edited 1 year ago) (1 children)

    The curl command pulls data from a URL into your terminal. So you can actually go to cheat.sh in a web browser to see what the output would be (also wouldn't necessarily recommend doing this vs. blindly pasting commands, but in this case, perfectly safe!). It looks like a little Unix command helper tool.

    Why wouldn't you recommend this? As a novice, it seems to me like a safe way to check out what you're actually pulling in through curl