starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Reverse text not showing up properly when using screen over ssh #6212

New Issue
Closed
opened 2026-01-31 00:32:30 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:32:30 +00:00
Owner
Copy Link

Originally created by @DMLou on GitHub (Jan 30, 2020).

Whenever I run screen on a remote ssh session, the bottom line's reverse text as configured in my screenrc file doesn't seem to work properly. I use slightly customized versions of Solarized Light as my themes in both PuTTY and Windows Terminal. However, the same behavior appears even when using the default Campbell theme.

Environment

Windows build number: Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): 0.8.10091.0

Windows OpenSSH connection to CentOS 7 Linux box

Steps to reproduce

While I originally saw the issue when ssh'ing to a Linux machine, I noticed they also appear when running screen in a local Ubuntu session. I'm including both reproductions here.

Remote reproduction

  1. Use the attached screenrc.txt file as the screen config file on the Linux host you're ssh'ing to
  2. ssh to the Linux host
  3. Run screen (screen -c screenrc.txt will override the default config with the attached file)

Local reproduction

  1. Use the attached screenrc.txt file as the screen config file on for your local Ubuntu session
  2. Start an Ubuntu session
  3. Run screen (screen -c screenrc.txt will override the default config with the attached file)

screenrc.txt

Expected behavior

The bottom line of the terminal should be in reverse text with the current screen highlighted, as shown in the attached PuTTY screenshot:

putty

Actual behavior

Reverse text doesn't work properly as shown in the attached screenshots from Windows Terminal. I've attached both my custom theme as well as the default Campbell theme.

windows terminal
windows terminal Campbell

Originally created by @DMLou on GitHub (Jan 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> Whenever I run `screen` on a remote ssh session, the bottom line's reverse text as configured in my screenrc file doesn't seem to work properly. I use slightly customized versions of Solarized Light as my themes in both PuTTY and Windows Terminal. However, the same behavior appears even when using the default Campbell theme. # Environment ```none Windows build number: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): 0.8.10091.0 Windows OpenSSH connection to CentOS 7 Linux box ``` # Steps to reproduce While I originally saw the issue when ssh'ing to a Linux machine, I noticed they also appear when running `screen` in a local Ubuntu session. I'm including both reproductions here. ## Remote reproduction 1. Use the attached screenrc.txt file as the screen config file on the Linux host you're ssh'ing to 2. ssh to the Linux host 3. Run `screen` (`screen -c screenrc.txt` will override the default config with the attached file) ## Local reproduction 1. Use the attached screenrc.txt file as the screen config file on for your local Ubuntu session 2. Start an Ubuntu session 2. Run `screen` (`screen -c screenrc.txt` will override the default config with the attached file) [screenrc.txt](https://github.com/microsoft/terminal/files/4134863/screenrc.txt) <!-- A description of how to trigger this bug. --> # Expected behavior The bottom line of the terminal should be in reverse text with the current screen highlighted, as shown in the attached PuTTY screenshot: ![putty](https://user-images.githubusercontent.com/3675305/73465332-3d1c5b00-434e-11ea-84e6-a6840e173ff0.png) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Reverse text doesn't work properly as shown in the attached screenshots from Windows Terminal. I've attached both my custom theme as well as the default Campbell theme. ![windows terminal](https://user-images.githubusercontent.com/3675305/73465330-3d1c5b00-434e-11ea-98db-824ac9940799.png) ![windows terminal Campbell](https://user-images.githubusercontent.com/3675305/73465333-3d1c5b00-434e-11ea-8e63-926eb6e7e78b.png) <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 00:32:30 +00:00
claunia commented 2026-01-31 00:32:30 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 30, 2020):

It would probably help if you attached a copy of the actual color scheme you are using (both for PuTTY and WT), because I don't think you'll get the effect you want with most standard color schemes.

The way screen works (as I understand it), the main window area is rendered with the default background color, while the status bar is rendered as "white" on "black". In most color schemes, the default background color is going to be the same as the "black" color, so the status bar will not be reversed. If you want to get that reversed effect, you'd need to set the default background to a light color, while leaving your "black" defined as a dark color.

That said, even with the color scheme setup correctly, it still won't work in Windows Terminal because of issue #293. It should work in a conhost shell though.

In short, I suspect this is a duplicate of #293 (or maybe #2661). I'd like to see the color scheme you're using to be sure though.

@j4james commented on GitHub (Jan 30, 2020): It would probably help if you attached a copy of the actual color scheme you are using (both for PuTTY and WT), because I don't think you'll get the effect you want with most standard color schemes. The way _screen_ works (as I understand it), the main window area is rendered with the default background color, while the status bar is rendered as "white" on "black". In most color schemes, the default background color is going to be the same as the "black" color, so the status bar will not be reversed. If you want to get that reversed effect, you'd need to set the default background to a light color, while leaving your "black" defined as a dark color. That said, even with the color scheme setup correctly, it still won't work in Windows Terminal because of issue #293. It should work in a conhost shell though. In short, I suspect this is a duplicate of #293 (or maybe #2661). I'd like to see the color scheme you're using to be sure though.
claunia commented 2026-01-31 00:32:31 +00:00
Author
Owner
Copy Link

@DMLou commented on GitHub (Jan 30, 2020):

That's fine. Here is the color scheme I'm currently using in WT:

{
            "name": "Solarized Light Custom",
            "foreground": "#073642",
            "background": "#FDF6E3",
            "black": "#FDF6E3", // For reversed text
            "red": "#DC322F",
            "green": "#859900",
            "yellow": "#B58900",
            "blue": "#268BD2",
            "purple": "#D33682",
            "cyan": "#2AA198",
            "white": "#073642", // For reversed text
            "brightBlack": "#000000",
            "brightRed": "#CB4B16",
            "brightGreen": "#586E75",
            "brightYellow": "#657B83",
            "brightBlue": "#839496",
            "brightPurple": "#6C71C4",
            "brightCyan": "#93A1A1",
            "brightWhite": "#c007a1"
        }

Note that I saw the same problem using the default Campbell scheme as well (albeit obviously with different colors), although I'm not ruling out that my tweaked scheme is also broken.

Here's the link to the PuTTY scheme I'm using: https://github.com/altercation/solarized/tree/master/putty-colors-solarized

@DMLou commented on GitHub (Jan 30, 2020): That's fine. Here is the color scheme I'm currently using in WT: ``` { "name": "Solarized Light Custom", "foreground": "#073642", "background": "#FDF6E3", "black": "#FDF6E3", // For reversed text "red": "#DC322F", "green": "#859900", "yellow": "#B58900", "blue": "#268BD2", "purple": "#D33682", "cyan": "#2AA198", "white": "#073642", // For reversed text "brightBlack": "#000000", "brightRed": "#CB4B16", "brightGreen": "#586E75", "brightYellow": "#657B83", "brightBlue": "#839496", "brightPurple": "#6C71C4", "brightCyan": "#93A1A1", "brightWhite": "#c007a1" } ``` Note that I saw the same problem using the default Campbell scheme as well (albeit obviously with different colors), although I'm not ruling out that my tweaked scheme is also broken. Here's the link to the PuTTY scheme I'm using: https://github.com/altercation/solarized/tree/master/putty-colors-solarized
claunia commented 2026-01-31 00:32:31 +00:00
Author
Owner
Copy Link

@DMLou commented on GitHub (Jan 30, 2020):

Oh, and I just tested it in a conhost shell and it worked fine.

@DMLou commented on GitHub (Jan 30, 2020): Oh, and I just tested it in a conhost shell and it worked fine.
claunia commented 2026-01-31 00:32:31 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 30, 2020):

OK, that makes sense. The PuTTY solarized scheme has a light background color and a dark black, so that would give you a "reversed" status line (and looking at the Windows Terminal schemes, I see that the light versions are setup that way too, but they won't work correctly until #293 is fixed). Your custom scheme above has the black and background colors the same, so I wouldn't expect it to show a reversed status.

@j4james commented on GitHub (Jan 30, 2020): OK, that makes sense. The PuTTY solarized scheme has a light background color and a dark black, so that would give you a "reversed" status line (and looking at the Windows Terminal schemes, I see that the light versions are setup that way too, but they won't work correctly until #293 is fixed). Your custom scheme above has the black and background colors the same, so I wouldn't expect it to show a reversed status.
claunia commented 2026-01-31 00:32:31 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jan 30, 2020):

And just to be clear, Campbell also has the black and background colors the same, so again I wouldn't expect it to show the reversed status. The same goes for most "dark" color schemes - there might sometimes be a slight difference in color between black and the default background, but it wouldn't be reversed like it is with a "light" scheme.

@j4james commented on GitHub (Jan 30, 2020): And just to be clear, _Campbell_ also has the black and background colors the same, so again I wouldn't expect it to show the reversed status. The same goes for most "dark" color schemes - there might sometimes be a slight difference in color between black and the default background, but it wouldn't be reversed like it is with a "light" scheme.
claunia commented 2026-01-31 00:32:31 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 31, 2020):

Yeah -- running this in conhost using the "experimental terminal settings" (where conhost tries to support 18 instead of 16 colors), I can see that the default background and the black status line are actually different. If they ever resolve to the same color value, Terminal will crush them into the same value.

This is definitely a /dup of #293 and #2661. Thanks all!

@DHowett-MSFT commented on GitHub (Jan 31, 2020): Yeah -- running this in conhost using the "_experimental terminal settings_" (where conhost tries to support 18 instead of 16 colors), I can see that the default background and the black status line are actually different. If they ever resolve to the same color value, Terminal will crush them into the same value. This is definitely a /dup of #293 and #2661. Thanks all!
claunia commented 2026-01-31 00:32:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 31, 2020):

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 (Jan 31, 2020): 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6212
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?