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

[vefatica]

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?

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.

[zadjii-msft]

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

[ghost]

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!

[vefatica]

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

[vefatica]

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.

[DHowett]

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

[DHowett]

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.

[vefatica]

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

[vefatica]

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

[vefatica]

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

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

Got any hints on fixing this?

[vefatica]

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:

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).