Vincent

Happened again today (after only one day of uptime). I tried `let b:coqtail_log_name = "/tmp/foo"` and `:CoqToogleDebug` but it didn't log anything. Rebooting solved the issue, but I'd like to...

it works for a (random) while and stops working. reboot fixes it I'll try the python thing next time I have issues.

It's happening again, I'm investigating: - `:CoqToggleDebug` then `:CoqStart` then `:echo b:coqtail_log_path` doesn't display a thing so I'm not sure where the log went :D - I ran your python...

None of my print in python code showed up. I tried line 329 of coqtail.vim and it shows `l:ok = 0` and `l:ver_or_msg = -1`. I'll try to dump more...

I left vim/coq for a meeting and when I was back, I managed to run Coqtail correctly, and now it won't start again. Still more questions :D

``` 2.284186 : raw key input: "t" 46 2.284253 : SafeState: reset: key typed 47 2.284293 : SafeState: Start triggering 48 2.284391 : looking for messages on channels 49 2.284430...

Nice addition, thank you ``` $ nc -zv localhost 62352 nc: connectx to localhost port 62352 (tcp) failed: Connection refused Connection to localhost port 62352 [tcp/*] succeeded! ``` I'm not...

I just tried the two `:echo` commands. They indeed return `fail`. I tried with bigger `waittime`, up to 6000 and it still `fail`. I waited a bit with `vim` still...

Never used NeoVim, that might be a good opportunity to do so ;) Thanks a lot for the support. I'll only update if I get meaningful info to debug.

I installed neovim today. I have a setup where vim can't start the plugin but nvim is fine :D I'll monitor if nvim ever fails (they share the same config/plugin)