So it's like a command line version of <a href="http://explainshell.com/" rel="nofollow">http://explainshell.com/</a> ...<p>And it seems like your site / API backend is not open source. Do you plan to make an offline version?
Awesome concept! I've never been a fan of looking up flags in another tab, and hunting down which ones are in use. Just seems like it should be an automatic process. The explainshell website is great, but it doesn't work offline. Fish's man page auto-completion is useful, but it lists all the flags, instead of the ones currently in use. If I could have this for every command out there, along with the binary's location/version at the top, I'd be a happy camper.
Why does it say "in the shell" when the actual work is done by a web server? Sorry, I was just really curious how you grep/awk/sed through some man pages.
<a href="https://www.mankier.com/?explain=%20sed%20-i#explain" rel="nofollow">https://www.mankier.com/?explain=%20sed%20-i#explain</a> doesn't parse sed right.
<a href="http://explainshell.com/explain?cmd=sed+-i" rel="nofollow">http://explainshell.com/explain?cmd=sed+-i</a> works much better
I'm not sure why it is defined as a function when a shell script would work as well, and prevents .bashrc clutter.<p>Also it doesn't understand traditional tar options, i.e.
explain 'tar xf filename'