Closed Cleancookie closed 1 year ago
@Cleancookie Hi, Thanks for this issue report. Hmmm, from the information in the log, it seems that the nvim process on the WSL side is successfully started, but the log is interrupted around the buffer display process. Thus, there is a possibility that goenovim is crashing due to some unexpected process at the time of nvim startup.
To isolate the problem, for example, if you execute the following command, does it work correctly?
goneovim.exe --wsl -u NONE
Running goneovim.exe --wsl -u NONE
does the same thing. A grey blank window appears then I can see neovim, then it closes
Tried goneovim.exe --wsl -u NONE --debug=./test.log
as well but unsure where the log file ends up, it's not in the current folder
edit:
thanks @shiena
@Cleancookie
Tried goneovim.exe --wsl -u NONE --debug=./test.log as well but unsure where the log file ends up, it's not in the current folder
Arguments after --wsl
are passed to nvim. So if you put the --debug
argument before that, the log will be specified on the windows side.
for example:
goneovim.exe --debug=./test.log --wsl -u NONE
Ah that makes sense - thanks!
I've edited my old comment to include the logs now
@Cleancookie What happens when the following command is executed from the cmd.exe ?
C:\WINDOWS\system32\wsl.exe $SHELL -lc nvim --cmd 'let g:gonvim_running=1' --cmd 'let g:goneovim=1' --cmd 'set termguicolors'
@akiyosi
Neovim just opens as normal, I see the following and it stays open:
I've tried running it with and without my neovim config too (same results) which is here: https://github.com/Cleancookie/dotfiles/tree/main/.config/nvim
@Cleancookie thanks for confirming. Could you please obtain debug logs with the following test binary to investigate this issue?
Recently, when I started wsl ubuntu on my windows11, I got a message prompting me to update with wsl --update
. Is that message the problem? When I ran wsl --update
the message disappeared.
@shiena Ah, that could be a possibility. That message is unexpected for the Neovim GUI, so there is a high possibility that it will crash. Ideally, the GUI would catch these unexpected messages and prompt the user to respond with a dialog or something...
@akiyosi
Output of those two debug logs are:
I haven't had a prompt to run wsl --update
yet but I ran it manually and it seemed to do something (it took maybe 1 minute to complete):
The debug logs were obtained after I ran wsl --update
@Cleancookie
I feel that the message output by wsl --status
is the cause of the error. Is there a message output before the prompt when running wsl -- bash -li
? There is no problem if it is only a prompt as shown below.
@shiena
I get this:
Powershell:
CMD:
@Cleancookie
The message on the Powershell side is motd, which is displayed only once a day. CMD is the second login, so the message is not displayed. If you run goneovim --wsl
in the current state, will it close immediately?
@shiena Just tried it and it still has the same problem. I've now added a .hushlogin file to disable it also
btw, just wanted to tank you both for all your time and patience
@Cleancookie Thanks for the info. The logs you gave in your comment, I think they are probably the logs output by the normal binary, since the logs you added are not output in the debug property. Could you please log again with the correct binary for debug?
oh sorry 🙈
@akiyosi just to double check im not doing something stupid I recorded a video of me doing it: https://www.loom.com/share/e11b479d9f8b4ec29af8bef0b5257a48
I'm not sure how to verify these logs contain the debugging info you need
These are the outputs:
@Cleancookie Sorry for not replying for so long. Also, I recently found out that the problem with the debug logs not being output was a bug in the CI script. My apologies to you for this as well.
I have fixed the CI script correctly and created a debugging artifact. I would appreciate it if you could reproduce the problem with this artifact and provide us with the debug logs.
OS: Windows11 goneovim: v0.6.3 nvim in wsl: v0.7.2
goneovim.exe --wsl
opens and closes almost instantly. If I try to open a folder then I can see netrw for a split second too before it closes.Below is output of
goneovim.exe --wsl --debug=$(here)/test.log
wherehere
is an alias forwslpath -w .