Wrong colors using emacs-nox in WT-Ubuntu
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- emacs, ubuntu
- Domain
- cli, operating-systems
Research direction
Start by comparing the attached screenshots for emacs-nox across MinTTY, MSYS2 bash in Windows Terminal, and Ubuntu in Windows Terminal, then reproduce the differing colors in the reported environments. Done means identifying and correcting the Windows Terminal behavior so Ubuntu matches the expected color scheme without regressing the other environments.
Written by the indexing model from the issue text.
Description
By default I use MSYS2 MinTTY and by means of wslbridge I use also this MinTTY for WSL Ubuntu. With both these apps I use a color scheme which I added to the profile.json:
{
"name" : "base16-default-mod-lighten",
"foreground" : "#D0D0D0",
"background" : "#151515",
"black" : "#151515",
"red" : "#AC4142",
"green" : "#90A959",
"yellow" : "#F4BF75",
"blue" : "#6A9FB5",
"purple" : "#AA759F",
"cyan" : "#75B5AA",
"white" : "#D0D0D0",
"brightBlack" : "#505050",
"brightRed" : "#C25E5E",
"brightGreen" : "#A6BB7B",
"brightYellow" : "#F8D5A5",
"brightBlue" : "#8CB5C6",
"brightPurple" : "#BE95B5",
"brightCyan" : "#97C7BE",
"brightWhite" : "#F5F5F5"
}
In the same profile.json I added the profiles for MSYS2 bash. I use the same above color scheme for MSYS2 bash and Ubuntu in WT.
In this attachment
emacs-nox-sshots.tar.gz
there are a few screenshots of emacs-nox running on various systems. As you can see I have the same good result in MinTTY (emacs-nox-mintty.png), Ubuntu in MinTTY (emacs-nox-mintty-Ubuntu.png) and in MSYS2 bash in WT (emacs-nox-WT-msys2.png). Instead in WT Ubuntu I get what I call bad result (emacs-nox-WT-Ubuntu.png).
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/terminal
-
Area-Settings Issue-Bug Priority-3 Product-Terminal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Area-Schema Help Wanted In-PR Issue-Task Product-Terminal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Issue-Feature Needs-Tag-Fix Needs-Triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Issue-Feature Needs-Tag-Fix Needs-Triage
Difficulty 3/5 1-2 days Newbie friendliness 66/100
-
Issue-Bug Needs-Triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/terminal
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·