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

Can I get bright without bold (as in a console)? #14644

New Issue
Closed
opened 2026-01-31 04:15:48 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 04:15:48 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Jul 22, 2021).

Microsoft Windows 10 Pro for Workstations
10.0.19042.1110 (2009, 20H2)
WindowsTerminal: 1.10.1933.0

Below, a Windows console is on top and in the foreground, WindowsTerminal on the bottom and in the background. This is the best size-match I can get ... Consolas 22 Normal in the console, Consolas 17 Normal in WT. Apparently, when I specify the bright/bold attribute in WT, I get both bright (a different color) and bold (a different font weight). In the console I get just the bright color.

Can I get bright without bold in WT?

image

I think something has changed recently. I've been looking at the bright green "v:>" prompt for ages, and only very recently has the fuzzy bold version of it bothered me.

Originally created by @vefatica on GitHub (Jul 22, 2021). Microsoft Windows 10 Pro for Workstations 10.0.19042.1110 (2009, 20H2) WindowsTerminal: 1.10.1933.0 Below, a Windows console is on top and in the foreground, WindowsTerminal on the bottom and in the background. This is the best size-match I can get ... Consolas 22 Normal in the console, Consolas 17 Normal in WT. Apparently, when I specify the bright/bold attribute in WT, I get both bright (a different color) and bold (a different font weight). In the console I get just the bright color. Can I get bright without bold in WT? ![image](https://user-images.githubusercontent.com/61856645/126679914-290d53fd-f8a8-4475-af68-baaa9921929b.png) I think something has changed recently. I've been looking at the bright green "v:\>" prompt for ages, and only very recently has the fuzzy bold version of it bothered me.
claunia added the Resolution-Duplicate label 2026-01-31 04:15:48 +00:00
claunia commented 2026-01-31 04:15:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2021):

I think something has changed recently.

yep, we added support for bold text in #10498.

Adding the setting to control this is in #10576, and the PR should be #10759 (unless someone snipes me).

/dup #10576

@zadjii-msft commented on GitHub (Jul 22, 2021): > I think something has changed recently. yep, we added support for bold text in #10498. Adding the setting to control this is in #10576, and the PR should be #10759 (unless someone snipes me). /dup #10576
claunia commented 2026-01-31 04:15:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 22, 2021):

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 (Jul 22, 2021): 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!
claunia commented 2026-01-31 04:15:49 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jul 22, 2021):

Here are the 1.9 preview (first) and the 1.10 preview (second) using the same settings file.

image

image

@vefatica commented on GitHub (Jul 22, 2021): Here are the 1.9 preview (first) and the 1.10 preview (second) using the same settings file. ![image](https://user-images.githubusercontent.com/61856645/126682224-f7d1dc23-5c05-487e-87cb-7e9d6cd20b96.png) ![image](https://user-images.githubusercontent.com/61856645/126682344-1f3c5212-5854-4aad-929c-8e16024b62b5.png)
claunia commented 2026-01-31 04:15:49 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jul 22, 2021):

yep, we added support for bold text in #10498

You not only added support for it, you made it the default, with no way to get the behavior to which users are accustomed, both in WT and the Windows console.

@vefatica commented on GitHub (Jul 22, 2021): > yep, we added support for bold text in #10498 You not only added support for it, you made it the default, with no way to get the behavior to which users are accustomed, both in WT and the Windows console.
claunia commented 2026-01-31 04:15:49 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 22, 2021):

We have to move forward. I'm not interested in making Terminal start up and act just like conhost in every single way.

@DHowett commented on GitHub (Jul 22, 2021): We have to move forward. I'm not interested in making Terminal start up and act just like conhost in every single way.
claunia commented 2026-01-31 04:15:50 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 22, 2021):

As well: Preview is a preview. We release features there to gauge how users will receive them 😄. We declared before even merging support for bold fonts that it needed to be configurable before we would take it out of the Preview version and into Stable.

@DHowett commented on GitHub (Jul 22, 2021): As well: Preview is a preview. We release features there to gauge how users will receive them :smile:. We declared _before even merging support for bold fonts_ that it needed to be configurable before we would take it out of the Preview version and into Stable.
claunia commented 2026-01-31 04:15:50 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jul 22, 2021):

I just changed my app alias to this (and I get this). Notice how the message box specifies the preview.

image

@vefatica commented on GitHub (Jul 22, 2021): I just changed my app alias to this (and I get this). Notice how the message box specifies the preview. ![image](https://user-images.githubusercontent.com/61856645/126686902-8cabfa37-bcec-40ed-bcb3-475e1cfd3d6c.png)
claunia commented 2026-01-31 04:15:50 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jul 22, 2021):

In the post above, I issued "WT" in the Win+R dialog. These are OK and both work correctly.

image

@vefatica commented on GitHub (Jul 22, 2021): In the post above, I issued "WT" in the Win+R dialog. These are OK and both work correctly. ![image](https://user-images.githubusercontent.com/61856645/126687771-aa186a35-73dc-4c75-a5f6-60286ba39a08.png)
claunia commented 2026-01-31 04:15:50 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jul 22, 2021):

So I uninstalled both. The preview would re-install but the release version gives this.

image
The unshown part of the reason is:
S-1-5-18 (0x80070005)

Got any hints on fixing this?

@vefatica commented on GitHub (Jul 22, 2021): So I uninstalled both. The preview would re-install but the release version gives this. ![image](https://user-images.githubusercontent.com/61856645/126695386-12b7295b-dc10-4fa6-9638-3b9268d10fc2.png) The unshown part of the reason is: ` S-1-5-18 (0x80070005)` Got any hints on fixing this?
claunia commented 2026-01-31 04:15:50 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Jul 22, 2021):

After a restart, I could (re-)install both versions (release and preview). But I'm still seeing peculiar behavior from the App Alias settings.

If I toggle these:

image

the Settings app remembers my choice but there are no changes in these registry keys:

2021-07-22 16:44:46.296  HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe
2021-07-22 16:44:41.597  HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe

If I manually change those keys (using .reg files) I can use the "WT" alias successfully if and only if what's in those keys matches the App Alias choice. If they don't match, I get the "access denied" message (regarding the one specified in the registry).

@vefatica commented on GitHub (Jul 22, 2021): After a restart, I could (re-)install both versions (release and preview). But I'm still seeing peculiar behavior from the App Alias settings. If I toggle these: ![image](https://user-images.githubusercontent.com/61856645/126708385-cddc608b-6fe3-4a97-8915-4b30569a090b.png) the Settings app remembers my choice but **there are no changes in these registry keys**: ``` 2021-07-22 16:44:46.296 HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe 2021-07-22 16:44:41.597 HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe ``` If I manually change those keys (using .reg files) I can use the "WT" alias successfully if and only if what's in those keys matches the App Alias choice. If they don't match, I get the "access denied" message (regarding the one specified in the registry).
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#14644
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?