Closed dev-zero closed 2 years ago
I've pushed a commit that seems to make this better; it will show up in the nightly downloads in ~30 minutes from now. Please give it a try and let me know how you get on!
@wez will do, thanks a lot!
ok, I've tested it with 40cb141a and it looks good now. What still puzzles me but is probably a different bug, is the selection on triple click: double click on text usually selects a word (depends on the emulator what it considers a word), but a triple click usually selects the complete line while wezterm selects only a part of the line (probably until a given max of chars?). See:
Yeah, this is expected behavior: triple click considers logical lines, but in order to constrain the cost of things like hyperlink rules that operate on logical lines, there is a maximum limit for logical line length. I know this isn't ideal.
As a potential alternative, I wanted to share that I use the configuration snippet shown here: https://wezfurlong.org/wezterm/config/lua/keyassignment/SelectTextAtMouseCursor.html
together with shell integration also linked in those docs, so that triple click gets me the entire section of text from the input/output semantic zone.
I'm going to close this as the original issue is resolved!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Describe the bug
When copying very long lines I get artificial line breaks inserted at wrong places.
Environment (please complete the following information):
To Reproduce
Steps to reproduce the behavior.
I select some very long content and then yank it with the middle-mouse, or I copy it with
ctrl+shift+c
and then paste it withctrl+shift+v
somewhere else then I get additional line breaks in the pasted output.Example:
becomes after the paste:
Resizing the window does a correct reflow and shows that there's no linebreak in the original output (depending on the window width the linebreak changes position)
Configuration
Expected behavior
No line breaks.