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

Italics are not rendered for terminal programs such as Neovim #7540

New Issue
Closed
opened 2026-01-31 01:06:44 +00:00 by claunia · 14 comments
claunia commented 2026-01-31 01:06:44 +00:00
Owner
Copy Link

Originally created by @edyu on GitHub (Apr 22, 2020).

Environment

Windows build number: 10.0.19608.0
Windows Terminal version (if applicable): 0.10

Any other software? Neovim and WSL2

Steps to reproduce

I have neovim installed on wsl2 and when I have configured neovim to render italics for comments. However, italics are not rendered when I use neovim when I run it in terminal mode in the windows terminal. I know that it's not a neovim problem because if I run it on alacritty for example, the comments are rendered in italics. I'm running neovim under WSL2 but I don't think it has any effect to this.

Expected behavior

Italics should render properly on the terminal.

Actual behavior

Italics are being ignored when rendering and fonts are only rendering in the "regular" style.

Originally created by @edyu on GitHub (Apr 22, 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. --> # Environment ```none Windows build number: 10.0.19608.0 Windows Terminal version (if applicable): 0.10 Any other software? Neovim and WSL2 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> I have neovim installed on wsl2 and when I have configured neovim to render italics for comments. However, italics are not rendered when I use neovim when I run it in terminal mode in the windows terminal. I know that it's not a neovim problem because if I run it on alacritty for example, the comments are rendered in italics. I'm running neovim under WSL2 but I don't think it has any effect to this. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Italics should render properly on the terminal. # Actual behavior <!-- What's actually happening? --> Italics are being ignored when rendering and fonts are only rendering in the "regular" style.
claunia commented 2026-01-31 01:06:46 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Apr 22, 2020):

One does not need WSL or NeoVIM to reproduce this . Attributes.ps1 will do, and indicates the currently missing SGR support.

@jdebp commented on GitHub (Apr 22, 2020): One does not need WSL or NeoVIM to reproduce this . [`Attributes.ps1`](https://github.com/jdebp/terminal-tests/blob/master/PowerShell/Attributes.ps1) will do, and indicates the currently missing SGR support.
claunia commented 2026-01-31 01:06:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 23, 2020):

That's right, we probably should add support for italics at some point in the future.

@zadjii-msft commented on GitHub (Apr 23, 2020): That's right, we probably should add support for italics at some point in the future.
claunia commented 2026-01-31 01:06:47 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 23, 2020):

Yep, we should add support for italic and faint and ~ ~ bold ~ ~ (don't ask, it's complicated).

@DHowett-MSFT commented on GitHub (Apr 23, 2020): Yep, we should add support for italic and faint and ~ ~ bold ~ ~ (don't ask, it's complicated).
claunia commented 2026-01-31 01:06:48 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Sep 16, 2020):

Italics is a very important missing feature, I feel. Alacritty supports it (@edyu mentions this). Even ConEmu supports this (and ConEmu is really old).

Cheers!

@rashil2000 commented on GitHub (Sep 16, 2020): Italics is a very important missing feature, I feel. Alacritty supports it (@edyu mentions this). Even ConEmu supports this (and ConEmu is _really_ old). Cheers!
claunia commented 2026-01-31 01:06:48 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 16, 2020):

Thanks for letting us know. In the future, you can register your support for an issue by using the 👍 button (or the Reactions) button if that button is not available.

@DHowett commented on GitHub (Sep 16, 2020): Thanks for letting us know. In the future, you can register your support for an issue by using the :+1: button (or the Reactions) button if that button is not available.
claunia commented 2026-01-31 01:06:48 +00:00
Author
Owner
Copy Link

@mowestusa commented on GitHub (Dec 10, 2020):

I did +1 this feature request, because I have observed this same behavior with the vim syntax highlighting of markdown. Vim comes out of the box configured to display for markdown files italics, bold, and bold/italics which I find very handy when I have large blocks of text written in markdown and I'm doing edits in the terminal. I'm loving using Ubuntu 20.04 in WSL 2 inside of Windows Terminal, but this one feature would be a huge quality of life improvement when you spend hours of your day editing markdown text in the terminal. Thanks for considering this feature, and thanks for the work that developers have already done on Windows Terminal.

@mowestusa commented on GitHub (Dec 10, 2020): I did +1 this feature request, because I have observed this same behavior with the vim syntax highlighting of markdown. Vim comes out of the box configured to display for markdown files *italics*, **bold**, and ***bold/italics*** which I find very handy when I have large blocks of text written in markdown and I'm doing edits in the terminal. I'm loving using Ubuntu 20.04 in WSL 2 inside of Windows Terminal, but this one feature would be a huge quality of life improvement when you spend hours of your day editing markdown text in the terminal. Thanks for considering this feature, and thanks for the work that developers have already done on Windows Terminal.
claunia commented 2026-01-31 01:06:49 +00:00
Author
Owner
Copy Link

@haininhhoang94 commented on GitHub (Jan 6, 2021):

since we already fixed/improve the issues, when will the next release include this commit (for either Release and Preview?

@haininhhoang94 commented on GitHub (Jan 6, 2021): since we already fixed/improve the issues, when will the next release include this commit (for either Release and Preview?
claunia commented 2026-01-31 01:06:49 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 6, 2021):

The next release will include this commit when it comes out.

@DHowett commented on GitHub (Jan 6, 2021): The next release will include this commit when it comes out.
claunia commented 2026-01-31 01:06:49 +00:00
Author
Owner
Copy Link

@Leandros commented on GitHub (Dec 30, 2021):

Is it possible to disable italics, in case my font doesn't support any italics?

@Leandros commented on GitHub (Dec 30, 2021): Is it possible to disable italics, in case my font doesn't support any italics?
claunia commented 2026-01-31 01:06:49 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 30, 2021):

Not in the terminal, but the application that's requesting the italics may have an option for that. In Neovim I think it's controlled by the color scheme.

@j4james commented on GitHub (Dec 30, 2021): Not in the terminal, but the application that's requesting the italics may have an option for that. In Neovim I think it's controlled by the color scheme.
claunia commented 2026-01-31 01:06:50 +00:00
Author
Owner
Copy Link

@bryant-the-coder commented on GitHub (Jan 7, 2022):

my italics is being cut off at the end of each letter. what should i do?

@bryant-the-coder commented on GitHub (Jan 7, 2022): my italics is being cut off at the end of each letter. what should i do?
claunia commented 2026-01-31 01:06:50 +00:00
Author
Owner
Copy Link

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

@bryant-the-coder Yep, they sure are, see #9381

@zadjii-msft commented on GitHub (Jan 7, 2022): @bryant-the-coder [Yep, they sure are](https://github.com/microsoft/terminal/issues?q=is%3Aissue+italics+cut+off), see #9381
claunia commented 2026-01-31 01:06:50 +00:00
Author
Owner
Copy Link

@k1ng440 commented on GitHub (Sep 5, 2022):

Its been 2 years still no fix :(

@k1ng440 commented on GitHub (Sep 5, 2022): Its been 2 years still no fix :(
claunia commented 2026-01-31 01:06:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 6, 2022):

@k1ng440 Italics support was added nearly two years ago: #8580. What specifically "has no fix"? The "italics get cut off some times" issue? That's tracked over in #9381

@zadjii-msft commented on GitHub (Sep 6, 2022): @k1ng440 Italics support was added nearly two years ago: #8580. What specifically "has no fix"? The "italics get cut off some times" issue? That's tracked over in #9381
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 Area-Rendering Issue-Task Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
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#7540
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?