Hello San Kumar! I looked at your source code, I was amazed that it was only one file, and only 100 lines of source code (less if we subtract whitespace). The

Hello San Kumar! I looked at your source code, I was amazed that it was only one file, and only 100 lines of source code (less if we subtract whitespace). The less source code a program has while still maintaining functionality and being readable, the better. Which brings me to my next point, functionality. You saw a problem, a big problem, which is that often even all of the features Unix has for help (man, apropos, etc.) are not sufficient to be able to quickly figure out how to complete a task, such that frequently people have to Google for answers, and why take the extra steps to go to a different window than the command line, search for answers, and return to the command line? It's extra steps, but more importantly, it breaks "flow". Also, this is one of the historic reasons that Unix lost the popularity battle with new/inexperienced users to Windows/Mac -- not enough user-friendly help, and this is especially true of Unix's historic command-line help systems. So, I applaud the problem you chose to solve, and I applaud the elegant way in which you chose to solve it! You are a true Hacker (used in the positive definition, not the negative)! So with respect to the problem you chose and the code that solves it, I say to you: Well played Sir, Well played! I vote that this code should become a standard part of all Unix distributions from now on.