Closed binarytrails closed 5 years ago
The tidalvim script when run tries to reattach to an existing tmux session. Try closing both the Vim and GHCI panes, or run tmux kill-session -t tidal
to kill the current session.
About the ghc: ConnectionClosed
, that looks like a problem with Tidal, I'm not sure what could be causing that. I would suggest doing also a pkill -9 ghc
just in case (note that the process is named ghc
not ghci
) and try running tidalvim again.
Yes, this makes total sense now.
I went to the root by trying to kill vim and it was surviving so I located it with ps aux | grep vim
and I saw tons of processes with ghc
and tmux
which led me to killall ghc
but vim stayed alive so for tmux
I ended up killing them by pid. If I encounter it again, I will try your suggestion of a more elegant way tmux kill-session -t tidal
which seems to be doing the same.
One interesting fact is that I deleted all tidalvim
files with backup, completely removed the plugin and verified that all the files were deleted but the loaded and freezed file persisted, I guess due to the tmux session in the memory.
Thank you for your prompt response!
I've come back to my setup; the jackd & supercolider are running without errors but when I launch tidalvim it freezes with an old file at screen and it says:
ghc: ConnectionClosed
; is there a way to flush its cache or force it to not load this file / start fresh? I tried to move all of my files to different location and I started looking into tidalvim script file but I'm quite unfamiliar with it...