this post was submitted on 15 Dec 2025
312 points (98.4% liked)

linuxmemes

28444 readers
1462 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.
    • 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, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 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.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    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
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    312
    cat posttitle.txt | grep meme (infosec.pub)
    submitted 1 day ago by alias_qr_rainmaker@lemmy.world to c/linuxmemes@lemmy.world
    43 comments fedilink hide all child comments
    you are viewing a single comment's thread
    view the rest of the comments
    [–] exu@feditown.com 15 points 22 hours ago (2 children)

    I prefer | less or less file.txt because I can search interactively

    [–] fartographer@lemmy.world 4 points 14 hours ago

    I prefer less until I find myself using less over and over again until I finally use cat so that I can just scroll up and review whatever I'm looking for.

    Is it the best or right way to do things? Nope, but it gets the job done just as good as anything else I do.

    And, it goes without saying, I do a terrible job of all of it.

    [–] somerandomperson@lemmy.dbzer0.com 10 points 22 hours ago (1 children)

    what about $EDITOR <(cat file)?

    [–] ulterno@programming.dev 6 points 19 hours ago (2 children)

    Well, when I can just do $EDITOR file...

    [–] jayands@lemmy.world 2 points 5 hours ago (1 children)

    The subtle difference is that your $SHELL is responsible for opening (and, iirc, parsing?) the file when you use \<, versus the $EDITOR being the responsible entity.

    [–] ulterno@programming.dev 1 points 1 hour ago

    Oh I get it now.
    Also, for some reason setting vi as $EDITOR, it is not able to load the contents of the file, unlike vim that does.

    [–] somerandomperson@lemmy.dbzer0.com 4 points 19 hours ago

    we're talking about a pipeline(-ish) thing here.
    so just out the cmd that you want to read the output of in the brackets