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

Re: [Issue 1291] Changed - Incorrect path in "not a working copy" error message.

From: Branko Čibej <brane_at_xbc.nu>
Date: 2003-05-08 04:55:42 CEST

cmpilato@collab.net wrote:

>issues@subversion.tigris.org writes:
>
>
>
>>http://subversion.tigris.org/issues/show_bug.cgi?id=1291
>>
>>*** Old
>>--- New
>>***************
>>*** 45,47 ****
>>--- 45,55 ----
>> the abspath would be nice.
>>
>> The /home/ralph line is definitely wonky...
>>+
>>+ ------- Additional Comments From brane@tigris.org 2003-05-07 18:40 PDT -------
>>+ "." is correct. We convert the canonical "" to the user-friendly "."
>>+ on output in a number of places, but not everywhere, it seems.
>>+
>>+ Actually, we should call svn_path_local_style whenever we output a
>>+ path (not an URL!), and that function should take care of the "" ->
>>+ "." conversion.
>>\ No newline at end of file
>>
>>
>
>I've not bothered to read the implementation promises of this
>function, but I'm concerned that calling svn_path_local_style on all
>output paths will make output be inconsistent in format from input.
>Because it's perfectly okay on Windows to use forward slashes for
>paths, I don't want this to happen:
>
> C:\> svn st -v wc/subdir
> _M 10 10 cmpilato wc\subdir
> M 10 10 cmpilato wc\subdir\file1
> A 10 10 cmpilato wc\subdir\subsubdir
>
Why not? This is what Windows users expect.

>Note the output path style that differs from the input. Perhaps we
>could store a bit in the context baton at the time we call
>svn_path_internal_style() saying that internal style was already in
>use or something. I dunno.
>
Yikes. Watch this:

    C:\> svn st -v wc/subdir\subsubdir/subsubsubdir\file13.5

How many bits do you want to store? :-)

>But to be reeeeeeally honest, I'd rather have the output be
>OS-independent so that wrapper scripts are instantaneously (more)
>portable.
>
Really? Which wrapper scripts?

    * Shell scripts: inherently non-portable, not worth the bother.
    * Python, Perl: Can handle both forward and backward slashes on Windows.
    * Emacs: ditto.
    * vi: don't know and don't give a damn.
    * Windows batch: non-portable, but can't handle forward slashes, so
      it's actually better to have the output in the correct format

You have no ides how happy I am that VMS is practically dead. Now _that_
file name syntax was a perfect mess. :-)

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 8 04:56:25 2003

This is an archived mail posted to the Subversion Dev mailing list.

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