Neal Becker writes: > Dan Nicolaescu wrote: > >> Neal Becker writes: >> >> > Dan Nicolaescu wrote: >> > >> > > Neal Becker writes: >> > > >> > > > hg status test_front_end_spec.py >> > > > *** failed to import extension rdiff: No module named > rdiff >> > > > ? test_front_end_spec.py >> > > > >> > > > The above warning confuses emacs. C-x v i report 'already >> > > > registered'. >> > > >> > > Indeed, vc-hg-status parses the result of "hg status >> > > test_front_end_spec.py" >> > > >> > > Is there are way to tell hg to ignore .hgrc ? I.E. something > like >> > emacs >> > > -q ? >> > > >> > > > After I fixed the above warning (removed rdiff from my > .hgrc), >> > then >> > > > C-x v i worked correctly. >> > >> > HGRCPATH= hg showconfig >> >> So should we run HGRCPATH= hg status by default in vc-hg-state? >> >> If yes, where else should we do it? > > Crossposting to mercurial devel. Anyone have suggestions? My gut > reaction is to say always use HGRCPATH='', but not really sure. That will indeed turn off customizations in ~/.hgrc. But the user will also lose the ui.username setting which might not be what you want when you make a commit :-) Brodie Rao has been working on an a patch that will allow you to set HGPLAIN to make Mercurial revert to 'plain' behavior: http://bitbucket.org/brodie/mercurial-crew-mq/src/tip/script-mode It will disable localization and reset verbose mode. However, it will not help you here: the user has mis-configured Mercurial by asking it to load an extension that does not exist. The warning will still be issued with Brodie's HGPLAIN patch. I think the best solution is to teach your mode to ignore these warnings From Mercurial. -- Martin Geisler VIFF (Virtual Ideal Functionality Framework) brings easy and efficient SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.