Differences
This shows you the differences between the selected revisions of the page.
| 2007-06-22 | 2007-12-29 | ||
| corrected grammar (be -> being) (24.206.117.246) | minor edits. (99.241.179.226) | ||
| Line 14: | Line 14: | ||
| ==== Opening Current Session in PuTTY ==== | ==== Opening Current Session in PuTTY ==== | ||
| If WinSCP's limited ability to [[remote_command|execute remote commands]] | If WinSCP's limited ability to [[remote_command|execute remote commands]] | ||
| - | does not meet your needs, you may let WinSCP open a shell session on the | + | does not meet your needs, you can let WinSCP open a shell session on the |
| - | same server in PuTTY client. Use command //Commands > Open in PuTTY//. | + | same server in a PuTTY client. Click //Commands > Open in PuTTY//. |
| - | By default, WinSCP creates temporary session settings for PuTTY (under name | + | By default, WinSCP creates temporary session settings for PuTTY (under the name·"WinSCP temporary session"). The session settings will contain only the options |
| - | "WinSCP temporary session"). The session settings will contain only options | + | |
| known by WinSCP, mostly connection options, but it will particularly lack | known by WinSCP, mostly connection options, but it will particularly lack | ||
| - | any terminal options, so defaults will apply. | + | any terminal options, so the defaults will apply. |
| - | If you want configure your own options, you can save PuTTY session settings | + | If you want to configure your own options, you can save PuTTY session settings |
| - | with the same name as WinSCP session. WinSCP will then open instruct PuTTY | + | with the same name as a WinSCP session. WinSCP will then instruct PuTTY |
| to open that session (It will not export any settings, not a connection | to open that session (It will not export any settings, not a connection | ||
| options). | options). | ||
| - | If WinSCP cannot find PuTTY executable in default path, you can setup path in [[ui_pref_integration#external_applications|preferences]]. Optionally you can also instruct WinSCP to send session password (if known) to PuTTY. However better approach would be to use [[public key]] authentication together with [[integration_app#pageant|Pageant]]. | + | If WinSCP cannot find the PuTTY executable in the default path, you can specify the path in [[ui_pref_integration#external_applications|preferences]]. Optionally you can also instruct WinSCP to send the session password (if known) to PuTTY. However a better approach would be to use [[public key]] authentication together with [[integration_app#pageant|Pageant]]. |
| - | You can also setup WinSCP to //[[ui_pref_integration#external_applications|Automatically open new sessions in PuTTY]]//. | + | You can also set up WinSCP to //[[ui_pref_integration#external_applications|Automatically open new sessions in PuTTY]]//. |
| ===== External Editor ===== | ===== External Editor ===== | ||