CommandCodeAI / CommandCodeAI/command-code

[Bug] C-x C-g to launch editor triggers visual artifacts

未關閉
#494 0 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

Summary

The Ctrl-x Ctrl-g shortcut, which launches the $EDITOR from the terminal, fails to register typed characters properly, it feels laggy and after pressing Enter multiple times or typing a colon (:), the terminal fills with colored lines and other visual artifacts. This disrupts the session and often requires multiple Ctrl-c keystrokes to exit CommandCode.

Environment
Operating System: Ubuntu 24.04.04 LTS
Shell: Bash 5.2.21
Terminal Emulators Tested: gnome-terminal, st
Terminal Multiplexer: tmux 3.4 (optional)
Editors Tested: vim 9.1, nano
No tmux used in some test runs

This may be a known issue, but no existing references were found.

Additional info
command-code@0.38.1

$ echo $TERM
xterm-256color

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
...
LC_NAME="en_US.UTF-8"
LC_ALL=en_US.UTF-8

$ echo $XDG_SESSION_TYPE
x11

Image Image
Expected Behavior

Typing characters should register immediately without lag or delay.
Typing a colon should behave normally (e.g., entering command mode in vim).
The terminal should remain clean and stable during the editing session.
Exiting the editor should return cleanly to the command-code prompt without visual artifacts.

Actual Behavior

Laggy/unresponsive keyboard input
Characters not registering properly
Terminal fills with colored lines/visual artifacts after pressing Enter multiple times or typing a colon
Disrupted session requiring multiple Ctrl-c to exit
Unstable terminal state

Steps to reproduce the issue

Open a terminal (gnome-terminal or st).
Press Ctrl-x Ctrl-g to launch the editor defined in $EDITOR.
Attempt to type text in the editor.
Press Enter several times or type a colon (:).

Command Code Version

0.38.1

Operating System

Linux

Terminal/IDE

st and gnome-terminal

Shell

bash

Additional context

No response

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

從 Ctrl-x Ctrl-g 編輯器啟動路徑開始,使用列出的終端、編輯器和 tmux 組合重現問題。比較啟動 vim 或 nano 後的輸入處理,接著確認字元能正常註冊、冒號和 Enter 能正確運作,且退出後會恢復乾淨的命令程式碼提示字元。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
bash, linux, vim
領域
cli, operating-systems
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。