hgrc.5.text FILES content, ordering implied?

Benoît Allard benoit at aeteurope.nl
Thu Aug 27 10:39:50 CDT 2009


Steve Borho wrote:
> On Thu, Aug 27, 2009 at 10:06 AM, Martin Geisler<mg at lazybytes.net> wrote:
>> Douglas Philips <dgou at mac.com> writes:
>>
>>> On or about 2009 Aug 27, at 4:11 AM, Martin Geisler indited:
>>>
>>>> The idea is to accumulate configuration values from different files,
>>>> loaded in order from least specific (/etc/mercurial on Unix) to most
>>>> specific (.hg/hgrc). I think that is fine as it is.
>>>>
>>>> The question is mostly if we should let hg read mercurial.ini on Unix
>>>> systems?
>>> I am very concerned by this, and looking at the code in windows.py, it
>>> sure has the feel of "Shaw, Pshaw, here's a smattering of files,
>>> you'll probably find -one- of 'em."
>>>
>>> Please explain the logic behind needing both mercurial.ini and .hgrc
>>> on Windows, in the same directory, and why it is better to extend that
>>> to non-Windows platforms than to fix Windows.
>> I'm not sure there is a "need" as such -- it is enough if Mercurial
>> would load one file on each system, especially now that a config file
>> can include other config files (so both .hgrc and Mercurial.ini could
>> include a file with common settings).
>>
>> Would you prefer Mercurial to load only Mercurial.ini on Windows and
>> only .hgrc on Unix, and that we deprecate the .hgrc file on Windows?
> 
> Does anyone run Mercurial on cygwin?  Does that platform use the
> windows version of util or the posix version?  The only reason to
> support ~/.hgrc on the Windows platform, IMHO,  is for cygwin.
> 

I don't know if it's using the windows or the posix version, but I can 
testify ~/.hgrc is read as confirmed by showconfig --debug and a dumb 
value in this file.

Regards,
Benoit


More information about the Mercurial-devel mailing list