[Bug 6039] New: The experimental evolution configs can silently prevent evolve from fully initializing

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=6039

            Bug ID: 6039
           Summary: The experimental evolution configs can silently
                    prevent evolve from fully initializing
           Product: Mercurial
           Version: 4.8.1
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: bug
          Priority: normal
         Component: evolution
          Assignee: bugzilla at mercurial-scm.org
          Reporter: matt_harbison at yahoo.com
                CC: lothiraldan at gmail.com,
                    mercurial-devel at mercurial-scm.org,
                    pierre-yves.david at ens-lyon.org

This is reproducible with both 4.6.1 (in the thg install), and 4.8.1 with
evolve loaded from a repository.  It feels a lot like issue5815, but I haven't
been able to confirm it yet.

A coworker had the following in Mercurial.ini, to support phabricator (without
evolve):

[experimental]
evolution = createmarkers, allowunstable


But on the command line when I was showing him how evolve worked:

$ /d/mercurial/hg evolve
hg: unknown command 'evolve'
(did you mean one of recover, remove, resolve, shelve?)

However, the help for the extension *is* loaded (i.e. `hg help evolve` prints
extension help, not the evolve command level help as expected).  Further,
pstatus and pdiff show up in the help, and can be run.

When using the modern syntax, it seems to work:

[experimental]
evolution.createmarkers = true
evolution.allowunstable = true

So it's not a big deal, but it was tough to recognize what was happening and
root cause it.  Maybe there's something that needs to be fixed in config
parsing and/or the extension loading sequence.

-- 
You are receiving this mail because:
You are on the CC list for the bug.