mirror of
https://github.com/espressif/esp-idf
synced 2025-03-09 09:09:10 -04:00
fix: recommend using Windows Terminal in case of issues with escape sequences
Closes https://github.com/espressif/esp-idf-monitor/issues/17
This commit is contained in:
parent
b2bc90d97a
commit
8318adb448
@ -154,7 +154,7 @@ void esp_console_repl_task(void *args)
|
||||
printf("\r\n"
|
||||
"Your terminal application does not support escape sequences.\n\n"
|
||||
"Line editing and history features are disabled.\n\n"
|
||||
"On Windows, try using Putty instead.\r\n");
|
||||
"On Windows, try using Windows Terminal or Putty instead.\r\n");
|
||||
}
|
||||
|
||||
linenoiseSetMaxLineLen(repl_com->max_cmdline_length);
|
||||
|
@ -160,10 +160,14 @@ Use UP/DOWN arrows to navigate through command history.
|
||||
Press TAB when typing command name to auto-complete.
|
||||
Your terminal application does not support escape sequences.
|
||||
Line editing and history features are disabled.
|
||||
On Windows, try using Putty instead.
|
||||
On Windows, try using Windows Terminal or Putty instead.
|
||||
esp32>
|
||||
```
|
||||
|
||||
### Escape Sequences on Windows 10
|
||||
|
||||
When using the default command line or PowerShell on Windows 10, you may see a message indicating that the console does not support escape sequences, as shown in the above output. To avoid such issues, it is recommended to run the serial monitor under [Windows Terminal](https://en.wikipedia.org/wiki/Windows_Terminal), which supports all required escape sequences for the app, unlike the default terminal. The main escape sequence of concern is the Device Status Report (`0x1b[5n`), which is used to check terminal capabilities. Any response to this sequence indicates support. This should not be an issue on Windows 11, where Windows Terminal is the default.
|
||||
|
||||
### No USB port appears
|
||||
|
||||
On Windows 10, macOS, Linux, USB CDC devices do not require additional drivers to be installed.
|
||||
|
@ -118,7 +118,7 @@ void app_main(void)
|
||||
printf("\n"
|
||||
"Your terminal application does not support escape sequences.\n"
|
||||
"Line editing and history features are disabled.\n"
|
||||
"On Windows, try using Putty instead.\n");
|
||||
"On Windows, try using Windows Terminal or Putty instead.\n");
|
||||
}
|
||||
|
||||
/* Main loop */
|
||||
|
@ -147,6 +147,10 @@ Use UP/DOWN arrows to navigate through command history.
|
||||
Press TAB when typing command name to auto-complete.
|
||||
Your terminal application does not support escape sequences.
|
||||
Line editing and history features are disabled.
|
||||
On Windows, try using Putty instead.
|
||||
On Windows, try using Windows Terminal or Putty instead.
|
||||
esp32>
|
||||
```
|
||||
|
||||
### Escape Sequences on Windows 10
|
||||
|
||||
When using the default command line or PowerShell on Windows 10, you may see a message indicating that the console does not support escape sequences, as shown in the above output. To avoid such issues, it is recommended to run the serial monitor under [Windows Terminal](https://en.wikipedia.org/wiki/Windows_Terminal), which supports all required escape sequences for the app, unlike the default terminal. The main escape sequence of concern is the Device Status Report (`0x1b[5n`), which is used to check terminal capabilities. Any response to this sequence indicates support. This should not be an issue on Windows 11, where Windows Terminal is the default.
|
||||
|
Loading…
x
Reference in New Issue
Block a user