Stefan Schwarzer

Thanks for the quick reply! :-) I don't know if it's relevant for reproducing the bug, but before the mentioned two posts I hadn't posted any message for over a...

Thanks for the fix! I still wonder why I couldn't edit the post anymore even after a few minutes. As far as I understand the code, the threshold is supposed...

> This is something I didn't experience in my using of the forum, i.e. I regularly edit my posts after I submit them. I believe you, but I experienced it...

I also (presumably) had crashes of `nimsuggest`. After that there was only basic syntax highlighting. Restarting `nvim` helped. There were no macros defined in the opened files. These problems happen...

> @sschwarzer @liquid600pgm > When something like this happen, can you record the outputs of the following for me? > > ```viml > :echo b:nimSugHighlight > :echo nim#suggest#FindInstance() > ```...

> @sschwarzer @liquid600pgm > When something like this happen, can you record the outputs of the following for me? > > ```viml > :echo b:nimSugHighlight > :echo nim#suggest#FindInstance() > ```...

> You can try restarting nimsuggest by stopping it :call nim#suggest#ProjectStop(), then do any random editing and it should respawn. This actually worked, thank you! :-) Could you possibly detect...

> That's really hard actually :( That's what I suspected. :-/ > The best way I could think of to debug this is to enable logging in nimsuggest, then use...

> Can you also add the `'--debug'` argument in? It's necessary to get detailed answer-response data from nimsuggest. Done :-)

I had some missing syntax highlighting today. However, nimsuggest still seems to be running and generates new output in the log file. Here's the data I could gather: ``` :echo...