C-x v i bug

[Dan Nicolaescu]

Brodie Rao <dackze at gmail.com> writes:

  > On Dec 3, 2009, at 6:01 PM, Martin Geisler wrote:
  > 
  > > Neal Becker <ndbecker2 at gmail.com> writes:
  > 
  > [snip]
  > 
  > >> 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
  > 
  > This patch is still highly experimental. There are some things I need to rework, and it's not really a solution you can use right now because it's against hg itself.
  > 
  > Setting HGRCPATH= is one option, but as Martin mentioned, you'll lose all user configuration: their username, ssh settings, diff options, merge settings, enabled extensions, etc.
  > 
  > Another option is to run all commands like this:
  > 
  > hg --config ui.debug=0 --config ui.quiet=0 --config ui.verbose=0 --config defaults.CMD= CMD

Let's first talk about the original problem that started this
discussion.
When a file in a directory that is under mercurial control is opened in
emacs, emacs runs "hg status FILE" so that it knows if it's registered
or not, if it's modified, etc.  
Any user settings in .hgrc should be irrelevant to the above.  Right?
It's desirable that this is as fast as possible, so processing .hgrc,
initializing plugins will just waste time.
After that emacs will want to know the version number for the file, for that
it runs "hg log -l1 FILE", and parse it from the output.
Any user settings in .hgrc should be irrelevant for this command.  Right?

[too bad that the status and version number are not available from a
single command...]