Explain Shell
explainshell.com
Explain Shell
1–10 of 179 posts
Re: Explain Shell
#2Very interesting project, already using it!
Re: Explain Shell
#3You can use `man test` for [ ] which it currently reports no man page for.
Re: Explain Shell
#4Very well done. Now I just wish this was a shell program!
user@server:~$ explain iptables -A INPUT -i eth0 -s ip-to-block -j DROPRe: Explain Shell
#5Gorgeous. Amazing. Absolutely fantastic. Easy the coolest and most useful thing I've seen on hacker news in a while.
Enough gushing, now some bug reports:
"read -r random_line "nc HOST PORT | tee movie.mp4 | mplayer -" I can hover over movie.mp4, but I can't scroll down the see the description without losing the emphasis on that path. I'd suggest letting the user click on the portion, or perhaps a long-hover effect?
Re: Explain Shell
#6This is amazing! It's great for someone like me who, while knowing their way around the shell, isn't as well versed as some of my more veteran co-workers. While it's great to hear explanations of some of the more dense lines they give me to run, that's not always possible and can be a bit annoying. This could help take some of the pressure off of them to drag me through. :P
Re: Explain Shell
#7WOW!
Re: Explain Shell
#8This is pretty cool but what I found annoying was matching the snippet of code and the description together. Take this for example: http://explainshell.com/explain?cmd=true+%26%26+%7B+echo+suc...
The command is: true && { echo success; } || { echo failed; }
But the top box description is for echo parameters. The next one is for echo. Why can't it go from top to bottom in order of the command? EG: Start with true, then &&, then {, then echo, etc.
The way it is, I spend a lot of mental energy matching things up.
Re: Explain Shell
#9Holy moly, this might be one of the best things I've seen on HN in a long time.
Re: Explain Shell
#10This is super cool