[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [bug] subwcrev

From: Jan Linnenkohl <jan.linnenkohl_at_gmx.de>
Date: 2006-06-13 21:22:05 CEST

Hi Per,

There is one constellation that is not working. But it is not a bug from
tortoisesvn!
It is just the backslash escape the quotation mark from the command
arguments.

This following constellations will work:

"C:\Cepa\New Folder\Cepa"
"C:\Cepa\New Folder\Cepa\."
C:\Cepa\New_Folder\Cepa\
C:\Cepa\New_Folder\Cepa

But not

"C:\Cepa\New Folder\Cepa\"

E.g. "C:\test\" "c:\test"
will bring inside of the program this:
1. C:\\test\" c:\\test
as the first and only argument
 
instead of
1. C:\test\
2. c:\test

The easiest way, when you are using Visual Studio is to put a dot behind, so
you didn't have an backslash at the end.
But may be it would be nice to put a nice error message, when the directory
name contain a quotation mark, e.g.

        Directory or file 'S:\Temp\TSVN" s:\test.in s:\test.out' does not
exist
        The WorkingCopyPath may be entered with an ending backslash and
inside quotation marks, e.g. "C:\test\"
        Please try to use a dot behind between the backslash and the
quoation mark, e.g. "C:\test\."

Jan

Per Rasmussen wrote:
> Looks like SubWCRev has a bug when used with paths containing spaces.
>
> To reproduce:
>
> C:\>"C:\Program Files\TortoiseSVN\bin\SubWCRev.exe"
> "C:\Cepa\New Folder\Cepa\"
> "C:\Cepa\New Folder\Cepa\AssemblyInfo.cs.in"
> "C:\Cepa\New Folder\Cepa\AssemblyInfo.cs" -e
>
> File 'Folder\Cepa\AssemblyInfo.cs.in C:\Cepa\New' does not exist
>
> Please CC me.
>
> I need this utility, so if anyone fixes it, a binary would be much
> appreciated :).

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Jun 13 21:24:42 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.