Differences
This shows you the differences between the selected revisions of the page.
| remote_command 2023-02-22 | remote_command 2025-04-17 (current) | ||
| Line 22: | Line 22: | ||
| Terminal emulation cannot be implemented at all as it is not possible to combine terminal emulation and file transfers in the same session. The reason is that with terminal emulation control characters have a special meaning that is interpreted by the server. On the other hand, the same characters (bytes) have special meaning in the file transfer protocols or may simply be present in the (binary) files being transferred. | Terminal emulation cannot be implemented at all as it is not possible to combine terminal emulation and file transfers in the same session. The reason is that with terminal emulation control characters have a special meaning that is interpreted by the server. On the other hand, the same characters (bytes) have special meaning in the file transfer protocols or may simply be present in the (binary) files being transferred. | ||
| - | If you happen to try to execute a command requiring terminal emulation, it will typically refuse to run with an error message like "Error opening terminal", "No TTY available", "stdin: is not a tty" or "Couldn't open /dev/tty for reading". | + | If you happen to try to execute a command requiring terminal emulation, it will typically refuse to run with an error message like //"Error opening terminal"//, //"No TTY available"//, //"stdin: is not a tty"// or //"Couldn't open /dev/tty for reading"//. |
| WinSCP may possibly support user input. However, most commands requiring user input does that via terminal emulation features. If your command needs plain input without terminal emulation you can use input redirection like: | WinSCP may possibly support user input. However, most commands requiring user input does that via terminal emulation features. If your command needs plain input without terminal emulation you can use input redirection like: | ||