-
Notifications
You must be signed in to change notification settings - Fork 22
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
Slow "start" (5s) when using it with WSL2 / Ubuntu 2204 #22
Comments
Thanks for posting this. I was having the same problem where a copy/paste would take a long time. Moving it outside of WSL2 fixed the issue for me as well. |
When you move win32yank to Windows host, do you need a specific configuration on NeoVim or Windows to use it? I assume you should add it to your PATH on windows (or linux)? |
I had it in my $PATH for my WSL terminal. But I can't check anymore, because I turned my back on windows. |
haha alright. No problem. |
yes, move to windows path solved |
It turns out every issue is always that `win32yank.exe` sucks when it lives in the WSL file system. Just move it to the Windows file system. See: equalsraf/win32yank#22
I am seeing the sane delay issue on my Windows 11 WSL-2 distros (both Debian and NixOS). I'm also seeing a data corruption issue. I downloaded the latest version of win32yank.exe to directory
When I am in that directory and run:
I get:
as expected,. However, if I run:
I get:
|
Hi,
I am just trying out this cool tool (thanks a lot for doing this work), and it takes around 5s to do anything with the it.
After some tinkering I found a solution: I've moved it form "somewhere" within the WSL distro to the windows part of the system and if was fast.
I am not sure if this is a me problem, but maybe it helps future people to solve a problem. I've attached a strace of both starts.
strace-fast.log
strace-slow.log
Best wishes, and thank you for this awesome tool <3
The text was updated successfully, but these errors were encountered: