61–70 of 179 posts
It had difficulty with:
find . -name ".cpp" | xargs -i grep -His "oops" "{}"
http://explainshell.com/explain?cmd=find+.+-name+%22*.cpp%22...
It seems to think the -His belongs to xargs rather than grep.
I did choke at the end of this little favorite:
find -name "*.[hc]" -o -name "*.[hc]pp"|xargs grep -siP 'apa'http://explainshell.com/explain?cmd=git Funny
The UI with the svg "wiring" is awesome. You should consider abstracting away that functionality so that it can be reused by other projects. Right now I'm imagining explainphys ;) where each term in a physics equation is explained e.g. The magnetic force felt by a particle of charge q moving with velocity \vec{v} in a magnetic field \vec{B} is \vec{F}_B = q \vec{v} × \vec{B} | | | | |______magnetic field magnetic for…
This is truly stunning. It's a small thing, and what it does is not stupendous. But the design, aesthetics, ease of use, in a word elegance makes the combined whole a superlative tool.
Earlier quoted context omitted.
Tried it. The explain read-out seemed reasonable. Care to elaborate how it wasn't informative?
The explanation for "du" and its -a flag make it sound like I'm trying to find out how much disk space my files are using. Fine, that's the usual usage, but the point here is that it lists out every file under the current directory. The bigger problem is grep. We're told that grep prints lines matching a pattern, great. But then the explanation of the arguments makes it sound, to the uninitiated, like I'm giving "foo…
I totally love this, it's already incredibly helpful! It's super-functional, and frankly it's very, very nice looking. To Mr. Idan Kamara, the creator of this, I have nothing but the highest praise! Now, I hate to get side-tracked, but for much larger commands, like this one: ps x -o "%r %c " | grep "someScript.sh" | awk -F' ' '{print $1}' | xargs -I % /bin/kill -TERM -- -% that has a lot of parts, it can be hard to…
:(){ :|:& };: or GTFO :)