1.13.10336.0 breaks Far Manager's output #16672

Closed
opened 2026-01-31 05:19:14 +00:00 by claunia · 9 comments
Owner

Originally created by @vblazhkun on GitHub (Feb 6, 2022).

Windows Terminal version

1.13.10336.0

Windows build number

19044.1466

Other Software

Far Manager 3.0.5800.0 x64

Steps to reproduce

Just run the application inside the terminal:

PS C:\Program Files\Far Manager> .\Far.exe

Screenshot 2022-02-06 192509

Expected Behavior

Screenshot 2022-02-06 193122

Actual Behavior

Corrupted output on the terminal.

Originally created by @vblazhkun on GitHub (Feb 6, 2022). ### Windows Terminal version 1.13.10336.0 ### Windows build number 19044.1466 ### Other Software Far Manager 3.0.5800.0 x64 ### Steps to reproduce Just run the application inside the terminal: `PS C:\Program Files\Far Manager> .\Far.exe` ![Screenshot 2022-02-06 192509](https://user-images.githubusercontent.com/7956686/152691037-d81cc725-32f8-46d2-bb3f-0e4ad70de073.png) ### Expected Behavior ![Screenshot 2022-02-06 193122](https://user-images.githubusercontent.com/7956686/152690930-a6d8abe2-bdf8-4ddd-877a-bfdf920f2d08.png) ### Actual Behavior Corrupted output on the terminal.
claunia added the Resolution-Duplicate label 2026-01-31 05:19:14 +00:00
Author
Owner

@237dmitry commented on GitHub (Feb 6, 2022):

It's good that the mouse and custom hotkeys have started working... Almost a/an year ago I already asked #9921. This is the only reason I use FAR in the standard Windows console. The same story with micro editor.

@237dmitry commented on GitHub (Feb 6, 2022): It's good that the mouse and custom hotkeys have started working... Almost a/an year ago I already asked [#9921](https://github.com/microsoft/terminal/issues/9921#issue-865188104). This is the only reason I use FAR in the standard Windows console. The same story with micro editor.
Author
Owner

@DHowett commented on GitHub (Feb 6, 2022):

It looks like somebody disabled ENABLE_VIRTUAL_TERMINAL_PROCESSING. What else is running in that terminal window?

We haven't changed the code here in quite some time, as it presents a significant compatibility risk.

/cc @alabuzhev for FAR

@DHowett commented on GitHub (Feb 6, 2022): It looks like somebody disabled `ENABLE_VIRTUAL_TERMINAL_PROCESSING`. What else is running in that terminal window? We haven't changed the code here in quite some time, as it presents a significant compatibility risk. /cc @alabuzhev for FAR
Author
Owner

@alabuzhev commented on GitHub (Feb 6, 2022):

@DHowett it's a duplicate of #11780.
@vblazhkun either update Far or turn off virtual terminal in interface settings.

@alabuzhev commented on GitHub (Feb 6, 2022): @DHowett it's a duplicate of #11780. @vblazhkun either update Far or turn off virtual terminal in interface settings.
Author
Owner

@vblazhkun commented on GitHub (Feb 6, 2022):

It looks like somebody disabled ENABLE_VIRTUAL_TERMINAL_PROCESSING. What else is running in that terminal window?

We haven't changed the code here in quite some time, as it presents a significant compatibility risk.

/cc @alabuzhev for FAR

I am not sure what has happened as the given application was working fine just before a recent update of the Windows Terminal. The second screenshot attached is from the stable version of the Windows Terminal [1.11.3471.0] with the exact same Far Manager and its settings.

@vblazhkun commented on GitHub (Feb 6, 2022): > It looks like somebody disabled `ENABLE_VIRTUAL_TERMINAL_PROCESSING`. What else is running in that terminal window? > > We haven't changed the code here in quite some time, as it presents a significant compatibility risk. > > /cc @alabuzhev for FAR I am not sure what has happened as the given application was working fine just before a recent update of the Windows Terminal. The second screenshot attached is from the stable version of the Windows Terminal [1.11.3471.0] with the exact same Far Manager and its settings.
Author
Owner

@vblazhkun commented on GitHub (Feb 6, 2022):

@DHowett it's a duplicate of #11780. @vblazhkun either update Far or turn off virtual terminal in interface settings.

Turning off the "Use Virtual Terminal for rendering" helped, but I do not get why was it working fine with the given knob ON just before the recent update of the Windows Terminal?

@vblazhkun commented on GitHub (Feb 6, 2022): > @DHowett it's a duplicate of #11780. @vblazhkun either update Far or turn off virtual terminal in interface settings. Turning off the "Use Virtual Terminal for rendering" helped, but I do not get why was it working fine with the given knob ON just before the recent update of the Windows Terminal?
Author
Owner

@vblazhkun commented on GitHub (Feb 6, 2022):

Is the issue related to #11690 committed to 1.13.10336.0?

@vblazhkun commented on GitHub (Feb 6, 2022): Is the issue related to #11690 committed to 1.13.10336.0?
Author
Owner

@237dmitry commented on GitHub (Feb 6, 2022):

Turning off the "Use Virtual Terminal for rendering" helped

It doesn't help in any way. FAR has completely changed the colors, and in the editor, as it was -- if you paste text with spaces, it moves out.

Rendering Turned On
far1

Turned Off
far2

Copy-Paste in editor. The same copy-paste in micro editor.
far3

@237dmitry commented on GitHub (Feb 6, 2022): > Turning off the "Use Virtual Terminal for rendering" helped It doesn't help in any way. FAR has completely changed the colors, and in the editor, as it was -- if you paste text with spaces, it moves out. Rendering Turned On ![far1](https://user-images.githubusercontent.com/78153320/152702649-eb06229c-6902-4410-b880-781f98fcb283.png) Turned Off ![far2](https://user-images.githubusercontent.com/78153320/152702584-b945c5f5-5836-43e1-ad3a-00cf27d394d6.png) Copy-Paste in editor. The same copy-paste in micro editor. ![far3](https://user-images.githubusercontent.com/78153320/152702587-2e7f4579-88ae-4af0-a51b-5df19d8679dc.png)
Author
Owner

@zadjii-msft commented on GitHub (Feb 7, 2022):

Yea, this is a /dup of #11780. Far was relying on some ill-defined terminal behavior. That behavior we clarified in 1.13, at the cost of breaking older FAR versions. They've since patched on their side, so people up-to-date on both should have a working experience again. Sorry for the confusion!

@zadjii-msft commented on GitHub (Feb 7, 2022): Yea, this is a /dup of #11780. Far was relying on some ill-defined terminal behavior. That behavior we clarified in 1.13, at the cost of breaking older FAR versions. They've since patched on their side, so people up-to-date on both should have a working experience again. Sorry for the confusion!
Author
Owner

@ghost commented on GitHub (Feb 7, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 7, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16672