Fix Korean IME composing text behavior on macOS

[devstefancho]

What do you want to change?

I want to fix a macOS Ghostty issue with Korean IME input.

Why do you want to make this change?

I use Korean input in Ghostty, and this problem happens during normal typing.

For example,
when I type "안녕하세요", the last syllable can still be in the composing state. Then If I press Enter at that moment, I expect the text to be committed and Enter to be handled, working at the same time.

In Ghostty, the composing text or the Enter action can be swallowed, so I need to press the key again or the input feels broken.
This is important for Korean users because this is a normal way Korean IME works on macOS. I would like to help fix this.

I acknowledge that:

• I have read the Contributing Guide and understand the contribution process.
• I have read and agree to follow the AI Usage Policy.
• I wrote this vouch request myself, in my own voice, without AI generating it.

[bo2themax]

I tired to type dks with 2-Set, Ghostty and Terminal behaves the same way, can you provide a way to test that Ghostty is behaving differently? Including how to type those characters would be great.

[devstefancho]

@bo2themax Yes, Terminal.app and iTerm2 behave the same, so Ghostty isn't doing anything wrong here. Sorry for this.

What I actually wanted to raise is Korean input specifically. Korean has no conversion or confirm step, each syllable is already final as you type it, so the Return that ends composition feels like it should also send the line, the way native macOS text views like TextEdit do.
But right now it needs a second Return, and the same thing makes Esc take two presses in vim.

You can see in this video, I typed twice to change line.

Screen.Recording.2026-07-06.at.8.19.40.PM.mov

I'd really like to see this improved. I understand not wanting to change the default when other terminals match it, so if a default change isn't something you'd want, would an opt-in option be acceptable?
That way it stays off unless someone turns it on. I've looked a bit into how the IME hands the key back after committing, so I'm glad to go deeper if it's a direction worth exploring.

[bo2themax]

I believe this's niche requirement that can be maintained in your fork. Right now I don't think we need to change this.

[devstefancho]

I'll take care of it in my fork. Thank you for looking into it.

[aca]

이슈들을 모아서 해결해보려합니다. #13750