-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening a file doesn't do anything #18
Comments
Apparently that's only the case with nvim. Zathura works fine for me, even though it takes like 5 seconds to open a file. I don't know whether it supposed to take that long or maybe I can speed up the process somehow. |
I think the speed really depends on your pc. As for nvim not working, I am assuming because it is not graphical in the same way other apps are. |
I have a decent computer, in fact I have Ryzen 7 7700X as the CPU, and the WSL, the distro, and the files I'm trying to open are all on m2, so it should be fine. So is it impossible to open nvim using OpenInWSL? I thought it wouldn't matter the nature of the application. |
Can you look in the log? Maybe there is the neovim startup error in there. Otherwise, I'll try to launch it myself later. |
The trial is over, I can't open anything anymore 😞 I'd appreciate if you would try it yourself. But actually though where would I find the OpenInWSL log anyways? If I can open it without the app I guess I can try to. |
The logs are in appdata/roaming/openinwsl/something.log. I don't remember the exact name. I'll try it. Sorry the trial ran out.. I don't think I have a way of extending it unfortunately :/ |
That's the whole main.log throughout my use of the program. It doesn't really look like it's different from what it says when I open zathura instead of nvim.
|
Just wondering, are you using any xserver or just wslg? |
I have no clue, I have installed WSL to test it, so I'm not really familiar with it. I think it will be using the default one the WSL comes with. |
I have installed trial version of the OpenInWSL from Windows Store, however anytime I try to follow any usage example it doesn't do anything, except saying
.txt >> Arch
.The distro that I have on my WSL is Arch, and I use nvim to open text files, so I tried to do using OpenInWSL. I had added a file association selecting Arch as the distro, and the command is the following:
nvim #fpth#
. If I try toTest Configuration
it doesn't do anything either, except, as said before, saying.txt >> Arch
.The distro is pretty fresh, I have installed it today, I don't think that something may be wrong with it.
The text was updated successfully, but these errors were encountered: