> From: Simon Large [mailto:slarge@slarge.plus.com]
> johan.stenqvist@skandia.se wrote:
>
> > This is my script:
> > @echo off
> > "%programfiles%\tortoisesvn\bin\subwcrev" "%1\"
>
> This is the error -----------------------------^
>
> You have escaped the closing quote out. If you want a
> backslash (which you shouldn't need anyway) you have to
> double it: "%1\\"
>
Hmm, you seem to be right - it does work when I remove the
last backslash - but since this is a batch script (.bat) I didn't
think you could escape with a backslash? And what about the other
backslashes in the path - I mean wouldn't they mean escapes as well?
This escaping thingy is something that's specific certain
programming languages - as far as I can remember windows
paths doesn't need to have double backslashes to avoid being
escaped, right?
Maybe subwcrev should be modified to properly escape path strings
passed to it as arguments? Or, at least have it's help message
indicating that you should only pass it properly escaped path strings.
As I got this working using only relative paths it's not a
big issue for me. But other people might find it useful - I first
used Visual Studio's ability to pass arguments such as the solution or
project path to a pre-build script, and it ends the paths with a single
backslash. I guess the same might be valid for other software suites as
well.
Best regards,
Johan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri May 27 14:32:06 2005