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: bugzi...@mercurial-scm.org Reporter: matt_harbi...@yahoo.com CC: lothiral...@gmail.com, mercurial-devel@mercurial-scm.org, pierre-yves.da...@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. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel