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

Re: @abc - Tag...

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-07-28 22:55:40 CEST

Thomas Beale wrote:
> Christopher Ness wrote:
>> On Thu, 2005-07-28 at 17:47 +0100, Thomas Beale wrote:
>>
>>> Max Bowsher wrote:
>>>
>>>> Thomas Beale wrote:
>>>>
>>>> Actually, the correct thing to do is to leave out the quotes. Which
>>>> aren't part of the syntax of autoprops at all.
>>>>
>>>> Max.
>>>>
>>>
>>> are you sure? I am no expert user, but I couldn't get this to work until
>>> I followed the advice of a recent poster and included the quotes and
>>> spaces. This is an extract from the config file I use, and substitution
>>> is definitely now working on my machine:
>>
>>
>> That would make sense, the command line `svn propset` would require the
>> quotes to keep the space separated list as a single argument. But that
>> is a bit of implementation detail that is likely not needed in the
>> config file.
>>
>> Have you tried it w/out quotes?
>>
>> Chris
>
> I have not, but without quotes, it will make it very hard to see the
> leading and traling spaces, which apparently subversion needs to have to
> properly parse the items in the list.

No!

The only reason you 'need' those leading and trailing spaces is *because*
you've put some bogus quotes into the property value. Otherwise Subversion
thinks you are asking it to activate keywords named $"Id$ and $Author"$,
which of course do not exist.
If you add the spaces, then you have a request to activate $"$, $Id$,
$Author$ and $"$ again - which does activate $Id$ and $Author$ as you
intended, but does so in a rather messy way.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 28 22:59:38 2005

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

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