Differences
This shows you the differences between the selected revisions of the page.
| 2014-04-10 | 2014-05-17 | ||
| different_account anchor (martin) | read-only ini file suggestion (martin) | ||
| Line 115: | Line 115: | ||
| If you want to protect your script from such inadvertent change, you should isolate its configuration from graphical mode explicitly. To do that [[config#export|export your configuration]] to a separate INI file and reference it using ''/ini='' [[commandline|command-line parameter]]. | If you want to protect your script from such inadvertent change, you should isolate its configuration from graphical mode explicitly. To do that [[config#export|export your configuration]] to a separate INI file and reference it using ''/ini='' [[commandline|command-line parameter]]. | ||
| + | |||
| + | Also consider setting the INI file read-only, to prevent WinSCP writing to it, when exiting. Particularly, if you are running multiple scripts in parallel, to prevent different instances of WinSCP trying to write it at the same time. | ||
| An ideal situation is when you are able to configure all the options you need using script commands only (''[[scriptcommand_option|option]]'' command, switches of other commands, [[session_url|session URL]] and [[rawsettings|raw site settings]]). Then you can force scripting mode to start with the default configuration using ''/ini=nul'', avoiding need for the INI file. | An ideal situation is when you are able to configure all the options you need using script commands only (''[[scriptcommand_option|option]]'' command, switches of other commands, [[session_url|session URL]] and [[rawsettings|raw site settings]]). Then you can force scripting mode to start with the default configuration using ''/ini=nul'', avoiding need for the INI file. | ||
| + | |||
| + | |||
| ===== Example ===== | ===== Example ===== | ||