Shift Double-click in tmux select words from differnet panes about terminal

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• wordDelimiters not working inside tmux with [shift]+[left mouse click] (#9382), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[carlos-zamora]

Thanks for filing! We're having trouble reproducing this. Would you be able to write up the steps required to get in this state /? This'll help us take a closer look 😊

[SivanagBalla]

@carlos-zamora Below is another screen shot where we can reproduce it -

Open a terminal - adjust the width to say 80 or less. Width shouldn't matter here but it makes easy to repro
Start a tmux session with two vertical split panes
Type some lengthy strings in both panes.
Now shift-doubleclick on a string on one pane - terminal will expand the selectoin to other pane.

My word delimiters are set to "()"',;<>!@#$%^&*|+[]{}?│"

[carlos-zamora]

Does this repro on Windows Terminal Canary?

[SivanagBalla]

Yes, just download (ver:1.22.1631.0) it and i can see the issue there also

[carlos-zamora]

We think this should be fixed by a combination of #15602 and some of the recent ConPTY work we've been doing. We're going to move the info over from that issue over here though since this has a nice test for it.

From what I understand, a row should only be marked as force-wrapped if we actually wrote past the last column, which naturally occurs already in the AdaptDispatch::_DoLineFeed call.

Removing the SetWrapForced call however breaks these unit tests:

ConptyOutputTests::InvalidateUntilOneBeforeEnd
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet0
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet1
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet2
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet3
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet4
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet5
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet6
TerminalCoreUnitTests::ConptyRoundtripTests::ResizeRepaintVimExeBuffer
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottom#metadataSet6
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottom#metadataSet7
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottom#metadataSet8
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottomLikeMSYS#metadataSet6
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottomLikeMSYS#metadataSet7
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottomLikeMSYS#metadataSet8

They break because when a ROW is not marked as force-wrapped the output behavior of the VtEngine and its output changes. We need to investigate why they break, what the correct behavior should be and how we can fix it. Presumably most unit tests simply assert the wrong behavior, but it's also possible that VtEngine::_PaintUtf8BufferLine and its removeSpaces variable may have to be updated.