3 ms·
It may not be for you but if you are going to take the piss, please at least give an example that does not generate a syntax error: ls | grep grep needs inp
by gerdesj 5y ago
It may not be for you but if you are going to take the piss, please at least give an example that does not generate a syntax error:
ls | grep
grep needs input and something to tell it what to do with the input.
I think Cult is a little harsh but it is handy to simply chain stuff together to quickly get something done. Along with the nominal concept of it's all files you can get an awful lot done in a shell with minimal effort.
Anything non trivial should get the full awk and sed treatment. The sort of system that has the GNU etc toolset available normally has python and perl available out of the box and probably php and a few more too - tools for the job. I also have something called pwsh that I dabble with - handy for fettling with VMware via Power CLI.
- eyelidlessness 5y ago> It may not be for you but if you are going to take the piss, please at least give an example that does not generate a syntax error I mean this kindly, as a person who struggles to infer implied details in a lot of circumstances: I think the quoted code was intended as shorthand, e.g. ls ... | grep ...
- gerdesj 5y agoI know but I think I touched a nerve 8)
- eyelidlessness 5y agoGross
- fouric 5y agoThat's exactly it. I've been running Linux as my desktop operating system for over a decade and know how to use grep - I just opted for shorthand (or may have underclocked some brain cells - I was in a hurry).