Characters are encoding gibberish all over the frontend

[fkukuck]

Description

GNOME Terminal v3.28.3-4.el8 has problems rendering the TUI.

See screenshot. It's unusable by me and I've downgraded to v0.15.31.

OpenCode version

1.0.61

Steps to reproduce

• Use GNOME Terminal v3.28.3-4.el8
• opencode
• be greeted with screen on screenshot

Screenshot and/or share link

Operating System

RedHat Enterprise Linus 8.10

Terminal

GNOME Terminal v3.28.3-4.el8

[github-actions]

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

• 1.0+ is unusable in non-truecolor terminal #3671: 1.0+ is unusable in non-truecolor terminal - Similar terminal rendering issues with older terminal versions
• Bug [Visual]: TUI populated with gibberish upon copying #2256: Bug [Visual]: TUI populated with gibberish upon copying - Same GNOME Terminal version experiencing gibberish characters
• [bug] opencode produces gabled text when input containing non-ascii characters #2593: [bug] opencode produces gabled text when input containing non-ascii characters - Character encoding issues causing garbled text

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

[kommander]

It thinks the terminal supports explicit width for some reason. These are explicit width sequences. The capability detection seems to be off here. I'll check that.

[inv1s10n]

Is there a solution to this problem? I am currently experiencing this issue in the latest version as well.

[fkukuck]

Install a different terminal, such as Konsole

[feghalya]

This is still an issue for me as well (GNOME Terminal v3.28.3 on RHEL8) with the latest opencode version (1.1.21) forcing me to use the old v0.15.31.

[kommander]

Can you get an opentui-examples release from https://github.com/anomalyco/opentui/releases/tag/v0.1.72 for you platform and run the "Keypress Debug Tool" and show me the capabilities it shows? shift+s should also write that out as json in the cwd.

[feghalya]

Is this what you're looking for?

[kommander]

Yes. Curious. It says it supports explicit width, but doesn't handle the escape sequences properly. I am getting a setup up to debug this properly.

[kommander]

Oh I just remembered, in the meantime you can try setting OPENTUI_FORCE_EXPLICIT_WIDTH=0, which might fix that.

[feghalya]

I tried that option and nothing seems to have changed. In case this is relevant: I've had similar characters in vim that were solved by setting set t_RK= t_TE=. Here is the issue that helped me solve it: vim/vim#11728.

Running gnome-terminal --version returns # GNOME Terminal 3.28.3 using VTE 0.52.4 +GNUTLS.