Freitag (forgot to login) wrote:

Or just pass using the "-load" command the same name session as is stored in WinSCP and users could rename their PuTTY sessions to match and this would let custom, per server/session, terminal settings be used instead of default.

This is what WinSCP already does. If it finds a PuTTY session with the same name as current WinSCP session, it uses that session (it does not even override username/password).

This is a request for a user version of PuTTY integration.

There is already the button to open a PuTTY session on the server using the stored ID and PW, but all sessions end up using the same default configuration.

If you could store some command line in WinSCP similiar to desktop shortstop for PuTTY

This is what the windows desktop shortcut takes to launch a named putty session.
"C:\Program Files\PuTTY\putty.exe" -load SESSION_NAME -l USER_NAME -pw PASSWORD

You are already passing a server_name, user_name, and password. If you could provide the option that in WinSCP I could enter the same name as the session in PuTTY that would be nice.

Or just pass using the "-load" command the same name session as is stored in WinSCP and users could rename their PuTTY sessions to match and this would let custom, per server/session, terminal settings be used instead of default.