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

Re: new experimental branch: dir-auto-props (issue 1989)

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-03-25 22:20:57 CET

On Friday 25 March 2005 07:27, philipp.marek@bmlv.gv.at wrote:
> > > But the subversion config file already has an ignore field that
> > > supports multiple file masks in one line: the global-ignores.
> > > Wouldn't it be consistent to allow the same syntax for an
> > > svn:ignore auto-prop?
> >
> > I believe it will. But having a bunch of stuff on a single line is
> > tough to read, especially, when you start working on a number of
> > projects. My 'global-ignores' line is somewhere around 400
> > characters long or more. I imagine at some point, my editor is going
> > to tell me it can handle the long line any more. :-)
> Looking through config.c I saw that lines may be broken by starting the
> next line with whitespace - something I didn't read in
> http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1 (maybe I
> just overlooked something)
> So you don't need such long lines.

Good to know!

> global-ignores is just whitespace-seperated; it would be inconsistent
> to use the same format for the auto-properties (as property
> \n-seperated, in the config-files with whitespace?)

I'm a little confused... why would it be inconsistent to have them both be
whitespace separated? Or at least follow the way auto-props are done
with files? *shrug*

> It would look like that:
> [dir-auto-props]
> * = *.o\n*.lo\n*.la\n*~\n
> That's not exactly what I call readable. But look at that:

Yeah, that's ugly.

> [dir-auto-props]
> * = *.o\n
> *.lo\n
> *.la\n
> *~\n
> That should be ok.

Eh. I'm not necessarily a fan of that either.

> The other possibility would be to concatenate multiple matching lines
> with an \n in between:
> [dir-auto-props]
> * = *.o
> *.tmp = *.tmp
> * = *.la
> * = *.lo
> I believe that we should require explicit \n (or whatever) and not just
> concatenate the property values.
> If noone tells me otherwise I'd propose to use that (and try to make a
> patch for that).
> But:
> Do we need unicode characters encoded? Are unicode-characters in
> filenames common? How should they be encoded with a \x??-syntax? Do we
> want to have them UTF8-encoded in the config-files?

Good question. I believe everything is expected to be UTF-8 in the config
file, but I haven't confirmed that at all.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 25 22:25:34 2005

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.