Support mode 2027/grapheme cluster handling

Open
#4,190 2 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

Read the linked Mode 2027 proposal and Unicode TR29 grapheme-cluster specification first. Then inspect Warp's Rust terminal rendering and input handling; done means complex graphemes such as क्षि, 👩‍🌾, 🏳️‍⚧️, and 각 are handled as clusters rather than individual code points.

Written by the indexing model from the issue text.

Description

enhancement triaged
Discord username (optional)

paperdave.net

Describe the solution you'd like?

Certain graphemes such as क्षि, 👩‍🌾, 🏳️‍⚧️, 각, and many more are made up of multiple unicode code points. These currently render as individual code points.

image

A good read on what is going on here is a blog post by Mitchell Hashimoto: Grapheme Clusters and Terminal Emulators. He's done alot of work to make this fast and reliable in Ghostty.

I am specifically requesting Warp to implement Mode 2027, a proposal for proper grapheme cluster support.

The specification for grapheme clustering describes exactly where graphemes break. Likely should find a library in the programming language Warp is built in, as the rules are very complicated and easy to get wrong.

Is your feature request related to a problem? Please describe.

No response

Additional context

I'm writing a terminal text input library and it would be great if Warp supported this, though I think for warp specifically I'm going to see if I

How important is this feature to you?

1 (Not too important)

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.