Well that's true, though it is the remote shell than chokes on the double semicolon. Will see if more people struggles with this.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- purefusion
I see what the issue was, now that I could see the actual command sent (had to enable logging).
The issue was, I had put semicolons after each command, including the last command. But WinSCP apparently already handles the last semicolon for you, so it was choking on [command];; (it wanted something between the two consecutive semicolons).
Of course, perhaps you could check for a trailing semicolon when users save their custom commands. Just a thought.
The issue was, I had put semicolons after each command, including the last command. But WinSCP apparently already handles the last semicolon for you, so it was choking on [command];; (it wanted something between the two consecutive semicolons).
Of course, perhaps you could check for a trailing semicolon when users save their custom commands. Just a thought.
- martin
Re: Custom Commands: Perform Multiple Commands on One Line
Please post a full log file showing the problem.
To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. For posting extensive logs you may use pastebin or similar application. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
- purefusion
Custom Commands: Perform Multiple Commands on One Line
I'd like to setup some custom commands that can do more than just one thing at a time. I have no problems doing this in the command line, using a semicolon to separate each command. Since this type of custom command chokes on semicolons, causing the connection to die and reconnect, I'd like to know if this is a bug that can be fixed, or if there's an alternate way to do multiple commands in one custom command in a WinSCP-friendly way?