this post was submitted on 05 Sep 2025
460 points (98.5% liked)

linuxmemes

27191 readers
2960 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.
    • 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
    460
    An awkward realization (startrek.website)
    submitted 3 days ago by MalikMuaddibSoong@startrek.website to c/linuxmemes@lemmy.world
    76 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] TheGingerNut@lemmy.blahaj.zone 13 points 3 days ago (2 children)

    Honestly I think 90% of people would never use awk if there was a simple preinstalled command for "print the nth column"

    [–] OpenStars@piefed.social 15 points 3 days ago* (last edited 3 days ago) (1 children)

    cut?

    [–] tal@lemmy.today 15 points 3 days ago* (last edited 3 days ago) (3 children)

    To be fair, a lot of the programs don't use a single character, have multiple spaces between fields, and cut doesn't collapse whitespace characters, so you probably want something more like tr -s " "|cut -d" " -f3 if you want behavior like awk's field-splitting.

    $ iostat |grep ^nvme0n1
nvme0n1          29.03       131.52       535.59       730.72    2760247   11240665   15336056
$ iostat |grep ^nvme0n1|awk '{print $3}'
131.38
$ iostat |grep ^nvme0n1|tr -s " "|cut -d" " -f3
131.14
$
    [–] TechLich@lemmy.world 8 points 3 days ago (1 children)

    I never understood why so many bash scripts pipe grep to awk when regex is one of its main strengths.

    Like... Why

    grep ^nvme0n1 | awk '{print $3}'

    over just

    awk '/^nvme0n1/ {print $3}'

    [–] FooBarrington@lemmy.world 12 points 3 days ago* (last edited 3 days ago)

    Because by the time I use awk again, I've completely forgotten that it supports this stuff, and the discoverability is horrendous.

    Though I'd happily fix it if ShellCheck warned against this...

    [–] ThunderLegend@sh.itjust.works 2 points 3 days ago

    This is awesome! Looks like an LPI1 textbook. Never got the certification but I've seen a couple books about it and remember seeing examples like this one.

    [–] MalikMuaddibSoong@startrek.website 1 points 3 days ago

    cut and tr are like the wonder twins of text munging

    Form of truncated whitespace! Shape of single whitespace! πŸ˜‚

    [–] laurelraven@lemmy.zip 4 points 3 days ago (1 children)

    This is definitely somewhere that PowerShell shines, all of that is built in and really easy to use

    [–] Laser@feddit.org 1 points 3 days ago (1 children)

    People are hating on Powershell way too much. I don't like its syntax really but it has a messy better approach to handling data in the terminal. We have nu and elvish nowadays but MS was really early with the concept and I think they learned from the shortcomings of POSIX compatible shells.

    [–] laurelraven@lemmy.zip 2 points 2 days ago

    I really can't stress enough how much power and flexibility comes with an object oriented shell, especially with the dotnet type system behind it.

    I think most people who hate it just do so either because it came from Microsoft (which... Yeah, that's understandable), or because it's a different way of thinking about it (and/or they spent a lot of effort learning how to parse data from strings effectively and hate that it's made easier?). But love or hate it, it is effective and powerful, and I find myself missing that when working with bash.