Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
p100sch14465yInteresting, happens to me by accident. Just the reality, that most of the time, you have to pipe the input to grep, conditions me to automatically write such commands.
-
I'm currently in the process of learning shell properly again, and this is something I'm trying to avoid.
-
@M3m35terJ05h to my knowledge, most programs can take the positional arguments as either the first or the last argument, so that shouldn't be an issue.
-
jdebs3365yI do it too because I don't have the foresight to realize what I want until I've already typed it. I think 'oh I'll just cat real quick' and then, several minutes later when I've finished typing the command, I think 'oh that file is way too big, I should grep' and here we are.
Does anyone else use:
cat /path/to/file | grep "blah"
Rather than:
grep "blah" /path/to/file
...when grepping? Or is it just me? Mainly asking because in my half asleep state I just wrote `tail -f | grep "blah"` by mistake and wondered why it was taking way to long to read the file...
rant