Differences
This shows you the differences between the selected revisions of the page.
| 2012-10-14 | 2012-10-14 | ||
| no summary (76.172.189.96) (hidden) | Restored revision 1346749454. Undoing revision 1350183486. (Petr) (hidden) | ||
| Line 17: | Line 17: | ||
| If there is command you need to execute regularly and in particular if the command works with files, you can find [[custom_command|custom commands]] useful. | If there is command you need to execute regularly and in particular if the command works with files, you can find [[custom_command|custom commands]] useful. | ||
| + | ===== [[limitations]] Technical Background of Terminal Limitations ===== | ||
| + | WinSCP does not support commands that require terminal emulation or user input. | ||
| + | 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 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 be simply present in the (binary) files being transferred. | ||
| - | ssh root@192.168.0.17 | + | If you happen to try execute command requiring terminal emulation, it will typically refuse to run with 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: | ||
| + | |||
| + | echo "some input" | command | ||