Maybe you forgot to install or source the completion files, or forgot to restart your shell after installing gWhisper.
The main reason is usability. As JSON uses characters also used by shells (mostly }{"), inputing an encoded datastructure would then require heavy escaping/quoting of those characters.
JSON is semi-human readable, however we found out that some aids can make datastructures even more readable, but are not possible in JSON:
- Horizontal guides indicating level of indentation for nested types instead of brackets.
- Vertical guides from identifier to value.
- Type information
- Colors
In the end we decided that machine-readability of gWhisper output is not really in the scope of gWhisper as a CLI debug tool. If we find out this functionality is really needed, we might add a flag to change this behavior
Not yet, but we are planning this for version v0.4.
Currently your server needs to have reflection enabled.
However we are working on a solution to load grammar from protofiles instead from reflection API.
We think that sub-shells ruin the experience. A small debugging tool should be controllable directly from the shell. So we decided to go the extra mile and find out how to dynamically pass completions into bash/fish. (Yes we had a lot of problems with arguments being tokenized)