[Notice] Known TTY/Stdin issues on Windows/WSL for specific prompts #9

New issue

Open

opened 2026-02-03 02:19:57 +00:00 by irammini · 0 comments

irammini commented

2026-02-03 02:19:57 +00:00

(Migrated from github.com)

Description:

While Mep is optimized for Linux, users on Windows and WSL may encounter specific terminal behaviors due to the way Windows handles stdin and ANSI escape sequences.

Known Issues:

TTY Freeze: The stdin buffer may become saturated, causing the prompt to appear unresponsive. This is most common in treeSelect, emoji, and seat after several prompt cycles.
UI Artifacts: In certain environments like CMD, Git Bash, and the VS Code Integrated Terminal, the UI may occasionally break or render incorrectly when handling complex, high-frequency input.

Affected Environments:

Windows 10 (PowerShell/CMD): Confirmed issues with TTY/buffer.
WSL: Inherits certain Windows console host limitations.
Windows 11: Performance remains untested; it is currently unknown if the new Windows Terminal fully resolves these TTY bottlenecks.
Third-party Terminals: Git Bash and VS Code terminals are particularly prone to UI glitches.

Workaround:
If the prompt hangs or the UI flickers unexpectedly, press Enter. This manually flushes the buffer, clears the "stuck" state, and usually restores the rendering.

**Description:** While **Mep** is optimized for Linux, users on Windows and WSL may encounter specific terminal behaviors due to the way Windows handles `stdin` and ANSI escape sequences. **Known Issues:** * **TTY Freeze:** The `stdin` buffer may become saturated, causing the prompt to appear unresponsive. This is most common in `treeSelect`, `emoji`, and `seat` after several prompt cycles. * **UI Artifacts:** In certain environments like **CMD**, **Git Bash**, and the **VS Code Integrated Terminal**, the UI may occasionally break or render incorrectly when handling complex, high-frequency input. **Affected Environments:** * **Windows 10 (PowerShell/CMD):** Confirmed issues with TTY/buffer. * **WSL:** Inherits certain Windows console host limitations. * **Windows 11:** Performance remains **untested**; it is currently unknown if the new Windows Terminal fully resolves these TTY bottlenecks. * **Third-party Terminals:** Git Bash and VS Code terminals are particularly prone to UI glitches. **Workaround:** If the prompt hangs or the UI flickers unexpectedly, press **`Enter`**. This manually flushes the buffer, clears the "stuck" state, and usually restores the rendering.