unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Neal Becker <ndbecker2@gmail.com>, emacs-devel@gnu.org
Subject: Re: C-x v i bug
Date: Thu, 3 Dec 2009 11:40:53 -0800 (PST)	[thread overview]
Message-ID: <200912031940.nB3JerkS027753@godzilla.ics.uci.edu> (raw)
In-Reply-To: <jwvmy1z7thb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 03 Dec 2009 14:25:03 -0500")

Stefan Monnier <monnier@IRO.UMontreal.CA> 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?
  > 
  > I haven't used Hg and don't know what you can put in .hgrc, so maybe I'm
  > way off base, but at least for Bazaar and CVS I think it would be wrong
  > to ignore the user's .cvsrc and .bazaar/bazaar.conf.

At least for vc-hg-state using HGRCPATH= is justfied:
1. vc-hg-state needs to be very fast, so not having to initialize
plugins should help.
2. the return value should not depend on whatever the user puts in .hgrc
(I think, I've never written a .hgrc file, so...)




      reply	other threads:[~2009-12-03 19:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 15:37 C-x v i bug Neal Becker
2009-12-03 16:04 ` Dan Nicolaescu
2009-12-03 16:35   ` Neal Becker
2009-12-03 18:28     ` Dan Nicolaescu
2009-12-03 18:37       ` Neal Becker
2009-12-03 23:01         ` Martin Geisler
2009-12-03 23:42           ` Brodie Rao
2009-12-04  5:34             ` Dan Nicolaescu
2009-12-04  9:37               ` Martin Geisler
2009-12-18 15:54                 ` Dan Nicolaescu
2009-12-18 16:49                   ` Matt Mackall
2009-12-18 17:40                     ` Dan Nicolaescu
2009-12-18 18:16                       ` Matt Mackall
2009-12-18 19:09                         ` Dan Nicolaescu
2009-12-18 19:38                           ` Matt Mackall
2009-12-18 20:08                             ` Dan Nicolaescu
2009-12-18 20:26                               ` Matt Mackall
2009-12-03 19:25       ` Stefan Monnier
2009-12-03 19:40         ` Dan Nicolaescu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200912031940.nB3JerkS027753@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=ndbecker2@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).