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

WSL support #73

Open
jacobrreed opened this issue Apr 5, 2024 · 6 comments · Fixed by #111
Open

WSL support #73

jacobrreed opened this issue Apr 5, 2024 · 6 comments · Fixed by #111
Labels
enhancement New feature or request Windows

Comments

@jacobrreed
Copy link

Currently using WSL sometimes, would be nice to be able to pass in commands to copy to clipboard, i.e i think to copy to windows clipboard you need something piped like output | clip.exe

@mistricky mistricky added enhancement New feature or request Windows labels Apr 7, 2024
@jhonnyV-V
Copy link

jhonnyV-V commented Apr 15, 2024

Hi @jacobrreed, I'm trying to fix this issue with this pull request #83, could be great if I could get some feedback or if you could test it, here is the branch, btw using clip.exe will not work at least not easily because is for text only, and if you disable windows env path in wsl you could not have access to clip.exe, I'm trying with powershell to access the clipboard

@jacobrreed
Copy link
Author

Hi @jacobrreed, I'm trying to fix this issue with this pull request #83, could be great if I could get some feedback or if you could test it, here is the branch, btw using clip.exe will not work at least not easily because is for text only, and if you disable windows env path in wsl you could not have access to clip.exe, I'm trying with powershell to access the clipboard

Will test it out later today after work thanks

@jacobrreed
Copy link
Author

jacobrreed commented Apr 15, 2024

image

Getting this error, its printing it out into the buffer for some reason but ya,

@mistricky
Copy link
Owner

Hi @jacobrreed, I'm not familiar with WSL and Windows stuffs, can you run CodeSnap.nvim on WSL propertly? As far as I understand it, this issue describes the CodeSnap.nvim installed on WSL correctly but cannot perform copy action? I received some issues which described their inability to run correctly CodeSnap.nvim on WSL, can you help me check this issue? looks like someone cannot install CodeSnap.nvim correctly on WSL.

@jacobrreed
Copy link
Author

I can give it a look, my install works fine, but on WSL specifically when i use CodeSnap to save to clipboard I get a Rust error that gets pushed into the current buffer oddly enough as shown in screenshot above

@jacobrreed
Copy link
Author

Replied to that thread, also to note for this issue, save to file works fine, its the copy to clipboard that doesnt, copying to clipboard instead of WSL shoots out the rust error, or quits neovim alltogether

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants