Open
Bug 1213145
Opened 10 years ago
Updated 9 years ago
./mach mercurial-setup doesn't understand the "hgext" syntax for specifying extensions
Categories
(Developer Services :: Mercurial: configwizard, defect)
Developer Services
Mercurial: configwizard
Tracking
(Not tracked)
NEW
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
I already had the following in my ~/.hgrc:
[extensions]
hgext.mq =
After mach made me run mercurial-setup, it has appended "mq = " to the list. It seems like it doesn't parse the above syntax so it couldn't detect my existing extensions.
Comment 1•10 years ago
|
||
The "hgext." prefix isn't necessary. Mercurial first tries to "import X" where "X" is the key from [extensions]. If that fails, "import hgext.X" is attempted. If that fails, you see a warning about the extension failing to load.
But this is still a bug in mercurial-setup.
| Reporter | ||
Comment 2•10 years ago
|
||
Oh, I see. I never understood why some recommended one or the other. :-)
Updated•9 years ago
|
Component: mach → Mercurial: configwizard
Product: Core → Developer Services
Version: unspecified → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•