[Bug] @ mention trigger fails after CJK characters (offset calculation error) #27293

Activity

1. github-actions

   assigned

   Hona

   on May 13, 2026
2. github-actions commented on May 13, 2026

   

   github-actionsBot

   on May 13, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Auto-completion does not support Chinese characters. #27290: Same bug report — @ mention autocomplete fails when preceded by Chinese (CJK) characters, same version (1.14.48)

   If this is the same issue, consider adding your additional details (the offset calculation pattern) as a comment on #27290 instead.
3. unomaas commented on May 15, 2026

   

   unomaas

   on May 15, 2026

   More actions

   Bumping this for visibility, +1.

   ---

   Reproduction with shift+return (newline) as trigger — same offset calculation bug

   I'm seeing the same "no results" behavior on @ autocomplete, but with a different trigger: newlines from shift+return.

   Repro steps (macOS, v1.15.0, Ghostty terminal):

   1. Open the TUI prompt
   2. Type @ on line 1 → autocomplete works, file picker appears as expected
   3. Press shift+return to insert a newline
   4. On line 2 (or any line after a newline), type @ → autocomplete shows "no results"

   The @ autocomplete works perfectly on the first line but breaks on every subsequent line after a shift+return newline. This is 100% reproducible — even a single newline before the @ is enough to trigger the failure.

   Why this is the same root cause:

   Issue #3734 (closed) identified the offset mismatch: visualCursor.offset counts differently than props.value.at. The reporter noted specifically that \n advances the cursor by 1 but Bun.stringWidth returns 0. The v1.14.49 fix for wide characters addressed the CJK case but did not fix the newline case.

   My tui.json uses the current keybinds format (not the deprecated keymap), so this isn't a config issue. The offset calculation for the @ trigger position is simply wrong when any \n precedes it in the input buffer.
4. github-actions commented on Jul 15, 2026

   

   github-actionsBot

   on Jul 15, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as not plannedon Jul 15, 2026