4 ms·
You completely skipped over reading his post, and thus your response makes no sense. Read the docs once, and write your weird syntax version as a shell script.
by papsosouid 14y ago
You completely skipped over reading his post, and thus your response makes no sense. Read the docs once, and write your weird syntax version as a shell script. Then you don't need to look it up ever again, because you are using the weird syntax you invented for yourself. It is just much simpler and easier to do it the reasonable way than to write it in javascript.
- scott_w 14y agoI didn't misread it at all. I just completely disagree that it's 10 minutes to work out how they all work. And that's every time you want to use them, because few people use them often enough to learn the tools properly.
- burntsushi 14y agoYou said: > The issue is that it's 5-10 minutes to scan each man page every single time I want to use sed, find, xargs, etc." Which means you could put in a one time investment, write a wrapper shell script, and be done. And if you insist on disagreeing still, then that's fine, but the this whole point was brought about in response to: > I've used CLI tools for years, and it would probably take me 5-10 minutes of scanning the man pages to reproduce all but the simplest of those snippets.
- mrb 14y agoYou keep saying that you have to research how they work every time. But we tell you: no, you only have to write the wrapper shell script once. It is a one-time effort. Just like harthur put a one-time effort in writing "replace". You wouldn't have to remember find/sed every time, just like harthur doesn't have to re-write "replace" every time.
- Sssnake 14y agoYou are the one who claimed 10 minutes. If you didn't misread, then you are deliberately ignoring what people are saying just to be obstinate.