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

New emojis (2021 Unicode 14.0+) cause rendering issues #3264

Open
Andriamanitra opened this issue Apr 24, 2024 · 1 comment
Open

New emojis (2021 Unicode 14.0+) cause rendering issues #3264

Andriamanitra opened this issue Apr 24, 2024 · 1 comment

Comments

@Andriamanitra
Copy link
Contributor

Andriamanitra commented Apr 24, 2024

Description of the problem or steps to reproduce

Open the following snippet, go to the second line and move cursor right. It is still highlighting the emoji. Move cursor right again and it will highlight 'x', but if you try to insert a character it will be rendered on top of the 'x' instead of before it. Once you move the cursor out of the line with the problematic emoji it will be rendered correctly again. Deleting characters on the line with the emoji will also cause weird rendering glitches.

🥲abc # emoji from Unicode 13.0, works ok
🫤xyz # emoji from Unicode 14.0, causes problems

The issue is caused by go-runewidth (which micro depends on) using an old Unicode specification. There is an open pull request to update it to Unicode 15.0 but the repo seems to not be very actively maintained.

Specifications

micro v2.0.14-dev
Commit hash: 18f3e1b
OS: Linux
Terminal: terminator 2.1.3

@JoeKar
Copy link
Collaborator

JoeKar commented Apr 24, 2024

There is an open pull request to update it to Unicode 15.0 but the repo seems to not be very actively maintained.

Hm, sounds like a fork is necessary.
Unfortunately we've no sufficient rights to place it into the most fitting place, which is the micro-editor organization.

@zyedidia:
I saw you did some work forking a newer tcell into the above mentioned org. What do you think about go-runewidth (or the rest of the dependencies in your space 😉)?

The best would be if it is updated upstream, but it doesn't look most likely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants