Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ligatures Move around and don't respect spacing #2490

Closed
JustinGrote opened this issue Aug 20, 2019 · 3 comments
Closed

Ligatures Move around and don't respect spacing #2490

JustinGrote opened this issue Aug 20, 2019 · 3 comments
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@JustinGrote
Copy link

Environment

Windows build number: 10.0.18956.0
Windows Terminal version (if applicable): 0.3

Steps to reproduce

Install FiraCode NF or another ligature font
Type ligatures

Expected behavior

Ligatures when typed, the console will move back appropriately.

Actual behavior

LigatureExample

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 20, 2019
@JustinGrote
Copy link
Author

This appeared to be a transient issue, after a reboot and futzing with the cmd font settings (may be unrelated) the spacing issue appears to have stopped. May be worth investigating still so I'll leave it open.

LigatureWorks

@DHowett-MSFT
Copy link
Contributor

Hey, does this still repro if you type test before the ligature? If so, this might be #633.

@DHowett-MSFT DHowett-MSFT added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Aug 22, 2019
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 26, 2019
@ghost
Copy link

ghost commented Aug 26, 2019

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed Aug 29, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Development

No branches or pull requests

2 participants