Rainer Schoenberger

OK, thank you for the reply. It is good to hear, that there is some awareness about the problem. Not adding a space after period will help in this special...

I think this is a good idea, however I do not yet completely understand the huge benefit of this approach in case of gWhisper: The `complete.bash` file is basically only...

this might also be a prereq for secure channel support #6 as we need some way to store credentials.

Idea: we could make CLI Options and config files basically the same thing. I.e. The config file is parsed with a sub-graph of the grammar and then added to the...

@callalilychen already did some work on this, which is in PR #67 However this currently is unfinished and introduces race conditions.

#83 introduced a work around for this issue.

OK After detailed analysis I traced this down to several problems of the Grammar Injector and all elements calling it. 1. Grammar injector did parse grammar for a candidate first...

behavior improved after fixing [#25]

Thanks for reporting this. We should indeed not crash but write an understandable error message. We did until now not test on non-reflection server. A;so see related issue: #5 which...

in latest development version, as well as in latest release v3.3.1 I cannot reproduce. output when connecting to non reflection server: ``` > gwhisper 127.0.0.1 Parse failed.Parsed until: '127.0.0.1' Possible...