Open jacobrreed opened 2 months ago
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
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
Getting this error, its printing it out into the buffer for some reason but ya,
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.
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
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
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