DEV Community

SEOKJUN LEE
SEOKJUN LEE

Posted on

Is your Android terminal eating your IME input? Here's a 30-second test

I'm a Korean user, and I type on a physical keyboard with Gboard. Several terminal apps I tried had the same problem: composing input broke. Syllables got eaten mid-composition, or committed wrong. So I built TermiPlus.

This isn't a Korean-only problem. It's a composing-input problem across Asian languages — anything where you build a character before committing it: Korean syllables, Chinese pinyin selection, Japanese kana conversion, Vietnamese telex. If a terminal mishandles the composing stage, all of them break the same way.

Before you switch terminals, run this 30-second test on the one you have now:

  1. Open your terminal app and switch to Gboard.
  2. Type slowly — in Korean, ㅎ, then 하, then 한 — and watch the composing underline. It should track your keystrokes until you commit.
  3. Now type a full word fast, the way you normally type.

The same test works in any composing language: pick a character from pinyin in Chinese, convert kana in Japanese, or type telex in Vietnamese. If the underline jumps, a character vanishes halfway, or a half-formed character gets committed early, your terminal is mishandling composing text.

Why it matters: this isn't cosmetic. In an SSH session a wrongly committed character is a wrong command. In a message it's a garbled sentence. And because it only shows up while composing — not in committed text — it's easy to blame the keyboard.

If your terminal fails the test, try TermiPlus (free APK, v1.0.16, Android 7.0+): https://github.com/nararajun/TermiPlus/releases — it handles composing input properly with a physical keyboard + Gboard. If something still feels off, open an issue on GitHub with your device, keyboard, and Gboard version and I'll look at it.

Top comments (0)