web.cacerts warnings with 1.7.3, how to fix and/or disable check?

Martin Geisler mg at aragost.com
Tue Jan 4 02:11:25 CST 2011


Mads Kiilerich <mads at kiilerich.com> writes:

> timeless wrote, On 01/04/2011 01:20 AM:
>> personally i expected:
>>     hg help web.cacerts
>> to work. i might look into that eventually, or not.
>
> That could be nice.
>
> I guess "hg help web" then should show the help for the whole web
> section ... but that would make "hg help diff" ambigious ... so ...
> perhaps not ...
>
> Mercurial do currently not have any knowledge of the hgrc help on
> runtime and there is no semantic markup of it, so integrating it into
> the help system isn't completely trivial.

It would be simple if we declare all the configuration settings in one
place like we do for commands in commands.py. However, when we talked
about this, Matt proposed that the settings should be defined where they
are needed -- so dirstate.py would declare the ui.slash setting since it
is only used in that file.

That, however, gives us a problem with demandimport: 'hg help ui.slash'
would only work if dirstate.py was loaded.

We could do some preprocessing where we import all Mercurial modules
unconditionally and dump the settings.

I can see how it is nice to declare config settings right where they are
needed, but it is also nice to collect them in one place for clarity.
Some settings are used in multiple places and then it might not be clear
where it should be declared -- if we have a single module for this, then
that small problem goes away.

> Such a project seems to have a lot in common with integrating the man
> pages with the hgweb help.

Yes, somewhat -- the project would result in having the source of the
hgrc.5 man page spread out over the code base.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/


More information about the Mercurial-devel mailing list