Skip to content
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

Open
KervyN opened this issue Apr 25, 2024 · 6 comments
Open

Slow "start" (5s) when using it with WSL2 / Ubuntu 2204 #22

KervyN opened this issue Apr 25, 2024 · 6 comments

Comments

@KervyN
Copy link

KervyN commented Apr 25, 2024

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

@GWW
Copy link

GWW commented Apr 29, 2024

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.

@Nargonath
Copy link

Nargonath commented Jul 1, 2024

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)?

@KervyN
Copy link
Author

KervyN commented Jul 1, 2024

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.

@Nargonath
Copy link

haha alright. No problem.

@rickywu
Copy link

rickywu commented Jul 22, 2024

yes, move to windows path solved

qstrahl added a commit to qstrahl/.vim that referenced this issue Sep 15, 2024
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
@mwoodpatrick
Copy link

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

/mnt/c/Users/mlwp/Software/win32yank-x64_dist/

When I am in that directory and run:

 echo "hello brave new world!" | ./win32yank.exe -i
 ./win32yank.exe -o

I get:

hello brave new world!

as expected,.

However, if I run:

echo "hello brave new world!" | /mnt/c/Users/mlwp/Software/win32yank-x64_dist/win32yank.exe -i
 /mnt/c/Users/mlwp/Software/win32yank-x64_dist/win32yank.exe -o 

I get:

/mnt/c/Users/mlwp/Software/win32yank-x64_dist/win32yank.exe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants