Make sure WT can copy wrapped lines as a single line

[angelog0]

I created this profile (since WT 0.5),

{
            "guid": "{9c173dff-f524-43df-b40e-29953998c744}",
            "name": "MSYS2 Terminal",
            "commandline": "cmd.exe /c \"set MSYSTEM=MSYS&& set MSYS=winsymlinks:nativestrict&& C:/msys64/usr/bin/bash.exe --login\"",
            "hidden": false,
            "startingDirectory": "C:/msys64/home/user",
            "closeOnExit": true,
            "colorScheme": "MSYS2-Theme",
            "cursorColor": "#FD9D4F",
            "cursorShape": "filledBox",
            "fontFace": "Cascadia Code",
            "fontSize": 11,
            "historySize": 9001,
            "icon": "C:/msys64/msys2.ico",
            "padding": "8, 8, 8, 8",
            "snapOnInput": true// ,
            // "useAcrylic": true,
            // "acrylicOpacity": 0.75
        }

and noticed that when I paste a long line as in
it works wrong

$ ls -lrt /usr/lib/gcc/ /usr/lib/gcc/ /usr/lib/gcc/ /usr/lib/gcc/ /usr/lib/gcc/ /usr/lib/gcc/ /usr/lib/gcc/ /usr/lib/gc
ls: impossibile accedere a '/usr/lib/gc': No such file or directory
[...]
$ c/ /usr/lib/gcc/ /usr/lib/gcc/

This does not occur in Ubuntu or DOS or PoweShell profiles.

In short, it does not like the end of line when using MSYS2 profile. Maybe you have some suggestions...

(BTW, I copied that line dragging the mouse and pasting with right click, as usually one have to do in WT)

The system is W10 Pro 64 10.0.18362.449.

[DHowett-MSFT]

This is due to a lack of wrapping copy, not paste.

[DHowett-MSFT]

Broadly, this is related to #780 and #2089.

[Biswa96]

Does this happen in latest cygwin also?

[angelog0]

@Biswa96, I do not use cygwin since 2014. The basic DLL in MSYS2 is the same version:

$ pacman -Ss msys2 | grep runtime
msys/msys2-runtime 3.0.7-6 (base) [installato]
msys/msys2-runtime-devel 3.0.7-6 (msys2-devel) [installato]

BTW, in MinTTY-MSYS2 it works as expected, without problems (the same as in Ubuntu-WT or CMD-WT profiles).

See the MSYS2 profile I posted above, may be it need some adjustment? Some other environment variable or what else?

[Biswa96]

Try this "commandline": "C:\\msys64\\usr\\bin\\bash.exe -i -l".

[angelog0]

No, it has the same issue. Beside this, I need to set those environment variables.. How with the command line you suggest?

[angelog0]

BTW, the default profile (defaults.json) sets

"initialCols": 120,

but in MSYS2 profile they, really, are 119. See
while in Ubuntu profile, effectively, they are 120. See

I typed 34567890 and copy/pasted 1234567890 up to the second line. notice the bigger gap for MSYS2...

[fanvinga]

This problem also exists for me. For me, the scenario that caused the issue was that I tried to copy the Dockerfile cross-line command to the Windows Terminal (WSL2), there would be extra blank lines, and bash would be recognized as a one-line command.

[angelog0]

Same issues with WT 0.7...

[fanvinga]

@angelog0 0.7.3291 seems to have solved the cross-row copy issue I complained about earlier

[angelog0]

The issue seems related to TERM variable.

When one starts MSYS2 with the launcher msys2.exe, TERM results equal to xterm. In WT it is set to cygwin.

Now if I use in the WT profile

"commandline": "cmd.exe /c \"set TERM=xterm&& set MSYSTEM=MSYS&& set MSYS=winsymlinks:nativestrict&& C:/msys64/usr/bin/bash.exe --login\""

the issue seems fixed and the line is 130 craracters long but Emacs in terminal (msys/emacs 26.3-1) has issues: its window displays garbage and the colors are not so good.

[Biswa96]

How about TERM=xterm-256color?

[angelog0]

No, it is worse.

For completeness, I have attached the result with MinTTY-TERM=xterm, WT-TERM=xterm, WT-TERM=xterm-256color. emacs-WT.tar.gz

[angelog0]

For the sake of completeness, the issue is still active in the last 0.7.3382.0 WT release...

[DHowett-MSFT]

@angelog0 thank you. Since this isn’t a bug and requires actual investment to make the line wrapping feature work, we aren’t likely to fix it accidentally. We will definitely close this workitem when we know it to be complete.

[angelog0]

Sorry, you have closed this

@msftbot bot closed this in #4415 19 days ago

but ALL defects I flagged here and here

are present in Windows Terminal Preview 0.10.761.0.

Are you sure you have rightly test the fix before to establish the issue was fixed?

BTW, #4415 is also cited here...

[DHowett-MSFT]

Okay: as far as I can tell, your shell is inserting a manual line break one character before the console would word-wrap. It's inserting a literal manual line break, so there's no hope that WT can recover from that.

If I emit the contents of a long text file to the screen, it writes all the way up to the right edge and copies out of WT as a single line.

If the application emits its own newline because it misunderstood the size of the screen, it writes all the way up to the newline and copies out of WT as two lines.

As long as they're doing that, by literally telling us to break the line, there isn't anything we can do to repair it.

We've fixed all other known cases of broken line wrap on copy/paste.

[angelog0]

@DHowett-MSFT you are missing that only in WT that occurs. In MinTTY and other terminals copy/past of long lines works as expected. Admitting your conclusions would admit that WT is not usable as terminal with MSYS2 and friends. Maybe I will switch back to MinTTY because this is an issue tha causes many trouble to me.

[DHowett-MSFT]

I can't help that msys has a special contract with MinTTY. If you do this in the traditional windows console, it has the same behavior. This is 100% an application bug.

Conhost has supported line wrapping for five years -- it also works for every other application that correctly prints to the edge of the screen. It might be time for MSYS to reconsider how it interacts with the console.