50
submitted 1 year ago by starman@programming.dev to c/foss@beehaw.org
you are viewing a single comment's thread
view the rest of the comments
[-] SWW13@lemmy.brief.guru 2 points 1 year ago

You can do most things by combining simple cmdline tools. E.g. filter out some specific lines from all files in a directory, get the value after the second :, write those to another file and then sort, deduplicate and count them.

This may sound complicated, but it's pretty easy and fast if your are familiar with a shell. To be that efficient with your shell you want it to actually be powerful and not just a plain text input. Also writing cmdline tools is rather easy compared to a usable GUI tool.

[-] smeg@feddit.uk 1 points 1 year ago

Genuine question: why not use grep, awk, sed, or any of the other gnu tools that can already do that?

[-] colournoun@beehaw.org 1 points 1 year ago

You could, but maybe a good shell makes it easier than the external tool. Or maybe you use the shell to effectively combine the inputs and outputs of the other tools.

[-] smeg@feddit.uk 1 points 1 year ago

I guess that's convenient if you're only ever on one machine, I prefer commands that work (almost) everywhere!

[-] colournoun@beehaw.org 2 points 1 year ago

Me too. I could never get into nushell or fish because they’re not posix and I don’t need to learn two ways to do something.

[-] SWW13@lemmy.brief.guru 1 points 11 months ago

That's what I meant, using your shell to run command line tools to solve your issue at hand. And having a powerful shell with e.g. context dependend autocomplete (and a lot more) helps to speed up that task.

this post was submitted on 21 Sep 2023
50 points (100.0% liked)

Free and Open Source Software

17626 readers
9 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS