Re: [svn] Problem with Peg Revisions and files containing '@'

On May 31, Eli Barzilay wrote:
>
> (submitting an issue, FWIW.)

OK, so it seems like this is impossible without registration, which
will not go through immediately. I'll post it here instead...

It seems like there is no way to escape a real `@' character which is
part of a file name. Looking at the code in
"subversion/libsvn_subr/opt.c", this behavior hard wired with no way
to avoid it. It also looks like standard escaping will not be
convenient since it's only needed for the last `@' in a filename.

The way to avoid this currently is to append a `@BASE' to the path.
If nothing else is changed, then its probably a good idea to mention
this in some docs. It would be better to actually come up with a
proper solution which can be used in scripts etc. I guess that having
a rule that the `@' is interpreted as part of a path if that path
exists is impossible when considering URLs.

So how about making an empty peg revision be used as the default?
Then the only escape that will be needed to guarantee proper behavior
in scripts is to use "path@".

Another thing that seems like it should be working is to use "path/".
It's questionable (IMO) whether this should be working, but it seems
to be working for plain file paths. However, with a `@', it fails
with the same

  svn proplist foo@bar/
  svn: Syntax error parsing revision 'bar'

which seems strange since the code in the above file look like it
stops as soon as it hits a `/'.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                  http://www.barzilay.org/                 Maze is Life!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org