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

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

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

Commencez par le chemin de lancement de l’éditeur Ctrl-x Ctrl-g et reproduisez le problème avec les combinaisons de terminaux, d’éditeurs et de tmux indiquées. Comparez la gestion des entrées après le lancement de vim ou nano, puis vérifiez que les caractères sont enregistrés normalement, que les deux-points et Enter fonctionnent correctement et que la sortie rétablit une invite de commande-code propre.