1

The idea is about allow to access to documentation like in KDevelop. KDevelop shown documentation of functions, when user hover mouse above it's invocation.

Kate will display documentation of command and files in this way. Documentation will be extracted from manual pages.

Why?
1. Improve security
2. Help developers/sysadmin using bash

History:
Before ExplainShell even started, I was creating partnership (sources on sourceforge.net). Partnership get listing in special language and translates it to bash script. Partnership requires to get input contains special file format to disallow to trick partnership. On output we got bash script, but partnership additionally compare commands/files with white list. This white list contains security level of program/file string pattern. When input doesn't match any pattern, it was supposed to be malicious. So partnership was some kind of security guard.

My idea is to improve security by similar way like partnership/ExplainShell. Beginners do not have skills to read bash scripts. Best option is to create special language, which makes creating malicious in it hard. And... be simple to read. Bash script do not pass any of this requirements, but when kate will explain, what selected command could do or what selected file/directory is supposed to contains, users will asks if obfuscated bash script is not malicious. And Kate will help to understood well-formed, simple to read, bash scripts.