[POLL] Mass renaming options for consistency + guidelines
yuya at tcha.org
Mon Nov 13 08:31:38 EST 2017
On Sun, 12 Nov 2017 12:26:18 -0500, Augie Fackler wrote:
> > On Nov 12, 2017, at 4:42 AM, Yuya Nishihara <yuya at tcha.org> wrote:
> > On Sat, 14 Oct 2017 14:02:03 +0900, Yuya Nishihara wrote:
> >> On Sat, 14 Oct 2017 00:41:04 -0400, Augie Fackler wrote:
> >>> durin42: +1
> >>> martinvonz: +1
> >>> David Demelier: +1
> >>> Yuya: ? (I think +0 on hyphens at least for new config knobs?)
> >> Yep, +0. More precisely:
> >> * okay: allow_pull
> >> * preferred: allow-pull
> >> * also preferred: allowpull
> >> FWIW, dashes can't be used in some config sections.
> >> * [hooks] - pre-/post- is reserved for command hooks
> >> * [revsetaliases], [templatealiases] - name must be a valid symbol
> > So we're agreed to do the mass renaming, right?
> > I thought it was only for new options, but maybe I was wrong.
> I’m happy to have aliases for things with the new config registrar, since it centralizes the list of aliases and greatly reduces the maintenance burden.
> I don’t feel strongly about renaming the canonical version in the docs though. If we think it’s better to leave the authoritative name the longer-standing name, that’s completely fine with me.
FWIW, introducing bunch of permanent aliases might not be as simple as it
sounds. It will basically add another axis to the current config layer,
[global, user, repo] * [oldname, new-name].
Should user's "ui.tweakdefaults" precede global "ui.tweak-defaults" for example?
Probably it should. Should they both be listed in "hg config"? Maybe, but how
can we know which is in effect? No idea...
More information about the Mercurial-devel