Differences
This shows you the differences between the selected revisions of the page.
| 2017-01-16 | 2018-05-31 | ||
| other_options explicit anchor (martin) | 5.13.2 Bug 1639 – Make WinSCP available in Microsoft Store (UWP/AppX package) (martin) | ||
| Line 35: | Line 35: | ||
| Check //Automatically open new sessions in PuTTY// to automatically send all sessions opened in WinSCP also to PuTTY. | Check //Automatically open new sessions in PuTTY// to automatically send all sessions opened in WinSCP also to PuTTY. | ||
| - | Use //PuTTY registry key// selection lets you choose registry key, where WinSCP exports its session settings, to be used by terminal client. WinSCP exports settings in PuTTY format, which is also used by many of its clones, such as [[integration_putty#kitty|KiTTY]]. If your terminal client does not support this format, you need to use respective patterns (i.e. ''!@'' and ''!U'') in [[#client_path|terminal client path]] box as an alternative way to pass the settings. The registry key path is also used by WinSCP when [[ui_import|importing sites]]. | + | Use //PuTTY registry key// selection lets you choose registry key, where WinSCP exports its session settings, to be used by terminal client. WinSCP exports settings in PuTTY format, which is also used by many of its clones, such as [[integration_putty#kitty|KiTTY]]. If your terminal client does not support this format, you need to use respective patterns (i.e. ''!@'' and ''!U'') in [[#client_path|terminal client path]] box as an alternative way to pass the settings. The registry key path is also used by WinSCP when [[ui_import|importing sites]]. The option is not available in [[microsoft_store|Microsoft Store installation]], where WinSCP uses only command-line switches to pass a limited set of session settings to PuTTY. |
| ===== Further Reading ===== | ===== Further Reading ===== | ||