Quoting "B. W. Fitzpatrick" <fitz@red-bean.com>:
> cmpilato@collab.net writes:
> > =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
<rant decorator=":-)">
Here we are, implementing a UTF-8-only library, but people are still using MUA's
that haven't the faintest idea about Unicode...
</rant>
> >
> > > Now, while the section names in the files are case-sensitive, those
> in
> > > the Windows Registry are not, so the top-level config key is being
> > > treated specially. Josef, what you wrote under subversion/proxies
> was
> > > getting parsed into the [DEFAULTS] section (yes, note the S; that's
> a
> > > bug, too, being fixed...); but even if it were the [DEFAULT]
> section,
> > > it's not the [default] section that the proxy code looks for. The
> > > names are case-sensitive on lookup!
> > >
> > > What Josef has to do is put the values in
> > >
> > > /machine/software/tigris.org/subversion/proxies/default
> >
> > Are you sure about this? I have a registry key with "DEFAULT" that
> > appears to be getting noticed. If I put bogus values in there,
> > Subversion throws a hissy fit about not being able to talk to the
> > proxy machine.
>
> I believe its the plural that is the problem, not the lowercase vs
> all-caps.
>
> that is DEFAULTS bad, DEFAULT good.
>
> -Fitz
Oops, yes, Fitz is right -- our options are case-preserving, but
case-insensitive. Which means that using [default] in the procxy config file
isn't a very good idea, becuase it conflicts with the intended meaning of the
[DEFAULT] section. How about [global] instead?
BTW, I fixed the DEFAULTS vs. DEFAULT typo.
Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 17 07:24:32 2002