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

clip.exe copy limit #133

Open
kkuhle opened this issue Nov 28, 2019 · 2 comments
Open

clip.exe copy limit #133

kkuhle opened this issue Nov 28, 2019 · 2 comments

Comments

@kkuhle
Copy link

kkuhle commented Nov 28, 2019

It seems that tmux-yank does not work for me in WSL with clip.exe if I am trying to copy over 1700-1800 lines. It may be related to the number of characters I'm copying so YMMV.

I thought there may be a limit in Windows with clip.exe, but I tested copying a file with around 3 million lines with "clip.exe < file" it works even if it takes a minute or two to complete.

Is there any chance there is some sort of limit imposed when using clip.exe?

@taylankasap
Copy link

Are you sure you're not counting the wrapped lines? Number on top right in tmux copy mode includes wrapped lines as multiple lines. If you're seeing 3000 on top right and when you paste to an editor and see 1700 lines, you might be thinking there's a limit but it's because of line wrapping.

@kkuhle
Copy link
Author

kkuhle commented May 27, 2020

@taylankasap no I was just using that as a reference to get an idea of the approximate lines. If I am over the limit, the clipboard just doesn't get overwritten using tmux-yank. That is opposed to cat somefilecontaininga100klines | clip.exe which works (takes a moment).

I'm wondering if tmux-yank has some timeout limit that if the application it's passing the text to (clip.exe) takes to long to complete and then we're left with none of it.

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

2 participants