Differences

This shows you the differences between the selected revisions of the page.

2015-12-17 2015-12-21
removing uses of batch abort and batch confirm not needed since 5.6 with release of the next major branch 5.8 (martin) 5.8 Bug 1373 Session can be named using /sessionname= command-line switch. (martin)
Line 6: Line 6:
winscp.exe site|workspace|folder winscp.exe site|workspace|folder
winscp.exe <session_url>[/path/[file]] winscp.exe <session_url>[/path/[file]]
 +winscp.exe [mysession] [/sessionname=<name>]
winscp.exe [mysession] [/newinstance] winscp.exe [mysession] [/newinstance]
winscp.exe [mysession] /edit <path> winscp.exe [mysession] /edit <path>
Line 37: Line 38:
The second creates the session specified by [[session_url|session URL]] and optionally by initial remote path. If the remote path is not ended by slash (''/''), it is treated as path to file (or even directory) that should be downloaded. The second creates the session specified by [[session_url|session URL]] and optionally by initial remote path. If the remote path is not ended by slash (''/''), it is treated as path to file (or even directory) that should be downloaded.
 +
 +Parameter ''/sessionname'' specifies a custom name of the session to be used instead of the automatically generated name in a format ''username@hostname'' or to override the name of the saved site. &beta_feature
If there's already idle WinSCP instance running, the session(s) opens in the existing instance. To force session open in new instance of WinSCP, use ''/newinstance'' parameter. If there's already idle WinSCP instance running, the session(s) opens in the existing instance. To force session open in new instance of WinSCP, use ''/newinstance'' parameter.

Last modified: by martin