anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

TUI editor hides some double-byte characters in the input field #1918

New Issue
Closed
opened 2026-02-16 17:33:14 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:33:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @nogataka on GitHub (Oct 2, 2025).

Originally assigned to: @adamdotdevin on GitHub.

  • Symptom
    Certain double-byte characters entered in the input field are not visible.

    This issue occurs because macOS’s native Terminal handles CJK full-width characters and combining marks more consistently, while VS Code and Cursor (VS Code–based integrated terminals, powered by xterm.js) are more prone to misalignment depending on configuration.

    (CJK stands for Chinese, Japanese, and Korean — languages that use full-width characters which typically occupy two cells in a fixed-width terminal.)

  • Steps to Reproduce

    1. Launch the TUI via the opencode command.
    2. Using a keyboard capable of double-byte input, enter four or more double-byte characters.
    3. Observe that some of the characters fail to render in the input field.

  • Expected Result
    All double-byte characters entered in the field should be displayed.

Here are screenshots:

Image Image
Originally created by @nogataka on GitHub (Oct 2, 2025). Originally assigned to: @adamdotdevin on GitHub. - Symptom Certain double-byte characters entered in the input field are not visible. This issue occurs because macOS’s native Terminal handles CJK full-width characters and combining marks more consistently, while VS Code and Cursor (VS Code–based integrated terminals, powered by xterm.js) are more prone to misalignment depending on configuration. (CJK stands for Chinese, Japanese, and Korean — languages that use full-width characters which typically occupy two cells in a fixed-width terminal.) - Steps to Reproduce 1. Launch the TUI via the opencode command. 2. Using a keyboard capable of double-byte input, enter four or more double-byte characters. 3. Observe that some of the characters fail to render in the input field. - Expected Result All double-byte characters entered in the field should be displayed. Here are screenshots: <img width="625" height="335" alt="Image" src="https://github.com/user-attachments/assets/79afdd7b-0fe6-4c05-8189-daa01fc87b83" /> <img width="599" height="92" alt="Image" src="https://github.com/user-attachments/assets/24f7a9ab-b995-4b1c-915c-26d32eabafbf" />
yindo closed this issue 2026-02-16 17:33:14 -05:00
yindo commented 2026-02-16 17:33:14 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 2, 2025):

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

  • #2904: Icons/Unicode characters cause file editing failures
  • #2593: [bug] opencode produces garbled text when input containing non-ascii characters
  • #2013: Korean characters disappear in the input prompt when using WezTerm/Ghostty
  • #379: Cyrillic characters are not displayed correctly in diff view

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 2, 2025): This issue might be a duplicate of existing issues. Please check: - #2904: Icons/Unicode characters cause file editing failures - #2593: [bug] opencode produces garbled text when input containing non-ascii characters - #2013: Korean characters disappear in the input prompt when using WezTerm/Ghostty - #379: Cyrillic characters are not displayed correctly in diff view Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:33:14 -05:00
Author
Owner
Copy Link
Copy Source

@jensenojs commented on GitHub (Nov 1, 2025):

fix on 1.0? @nogataka

@jensenojs commented on GitHub (Nov 1, 2025): fix on 1.0? @nogataka
yindo commented 2026-02-16 17:33:14 -05:00
Author
Owner
Copy Link
Copy Source

@nogataka commented on GitHub (Nov 5, 2025):

Thanks, the issue has been fixed.

@nogataka commented on GitHub (Nov 5, 2025): Thanks, the issue has been fixed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1918
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?