Repository navigation
Fix: A display of unicode composing characters by CoreText renderer - #680
Merged
Merged
Conversation
Reconstruct and use 'gui_macvim_draw_string' for CoreText renderer
|
Not totally sure, but I think this PR may have created a new bug: |
Member
Author
Contributor
|
Should we revert f53f990? |
Member
Author
|
I expect master...ichizok:fix/coretext-renderer can fix it (so need not revert). I will create PR soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To reconstruct and use
gui_macvim_draw_stringfor CoreText renderer.This PR will fix #400 #604 vim-jp/issues#1114.
Current:
Patched: almost fixed
'macligatures'doesn't work. (always ligatures at using FiraCode font) This may be undesirable?