How to disable character rendering like from '>=' to '≥', from '!=' to '≠' #15778

Closed
opened 2026-01-31 04:48:09 +00:00 by claunia · 3 comments
Owner

Originally created by @luooofan on GitHub (Nov 4, 2021).

Actually this is just my question about wt, maybe it can become a feature.

Description of the new feature/enhancement

Provide an option which controls the character rendering like from '>=' to '≥', from '!=' to '≠'
To be honest, it's a wonderful feature, but there are some unsuitable situations.
e.g. 'expr<...,...>=[...]'

Proposed technical implementation details (optional)

None

Originally created by @luooofan on GitHub (Nov 4, 2021). Actually this is just my question about wt, maybe it can become a feature. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement Provide an option which controls the character rendering like from '>=' to '≥', from '!=' to '≠' To be honest, it's a wonderful feature, but there are some unsuitable situations. e.g. 'expr<...,...>=[...]' <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) None <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 04:48:09 +00:00
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Nov 4, 2021):

AFAIK, this is can be configured in Font features. Or choose a font that does not define those ligatures.

@KalleOlaviNiemitalo commented on GitHub (Nov 4, 2021): AFAIK, this is can be configured in [Font features](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-appearance#font-features). Or choose a font that does not define those ligatures.
Author
Owner
@KalleOlaviNiemitalo commented on GitHub (Nov 4, 2021): See also <https://github.com/microsoft/terminal/issues/10525> and <https://github.com/microsoft/terminal/issues/759> and ["Font features and axes of variation" spec](https://github.com/microsoft/terminal/blob/39b72f78c3d10d0ef1d745608e67f69c28adfe6d/doc/specs/%231790%20-%20Font%20features%20and%20axes-spec.md).
Author
Owner

@luooofan commented on GitHub (Nov 4, 2021):

Thanks for your reply.
That's exactly what I want.

@luooofan commented on GitHub (Nov 4, 2021): Thanks for your reply. That's exactly what I want.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15778