Reword prompt/TUI clash bug description and clarify cmd vs conhost

This commit is contained in:
Isaiah Odhner 2023-07-21 13:03:18 -04:00
parent c70f3e35e3
commit bc3dba29fc

View File

@ -237,12 +237,13 @@ Textual Paint works with the new [Windows Terminal](https://learn.microsoft.com/
Ctrl+V does not work to paste, but **Edit > Paste** does work.
It may be possible to unbind Ctrl+V to fix this, see [this issue](https://github.com/microsoft/terminal/issues/11267).
Running in Powershell, there seems to be a bug where the powershell prompt will be active at the same time as the TUI,
and commands can be typed and run, and the output will be interwoven with the TUI.
Running a second instance of Textual Paint even causes oscillation between both instances as they redraw the screen.
I would recommend using Command Prompt (not the app, but the shell) inside Windows Terminal instead, available in the new tab dropdown menu.
Running in Powershell, you may run into a bug where the powershell prompt becomes active at the same time as the TUI.
Moving the mouse will redraw parts of the TUI, and it becomes hard to click on things, but still possible.
Commands can be entered, and the output will be interwoven with the TUI, including if you run a second instance of the program, in which case the two instances will vie for the screen.
If this happens, I would recommend first messing around with it, since it's a fun glitch, then opening a new tab in Windows Terminal with the **Command Prompt profile**, available in the new tab dropdown menu.
Textual Paint will not work properly with the old Windows console (`conhost.exe`), which lacks emoji/Unicode support and true color support.
This program is commonly thought of as the "Command Prompt", but the Command Prompt (`cmd.exe`) is actually a *shell* (like `bash`) that can run in either the old console or the new Windows Terminal, which are both *terminal emulators*.
### VS Code