From: Chong Yidong <cyd@stupidchicken.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Dan Nicolaescu <dann@ics.uci.edu>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: your vc-hg.el change
Date: Mon, 24 Nov 2008 10:52:23 -0500 [thread overview]
Message-ID: <87od05azpk.fsf@cyd.mit.edu> (raw)
In-Reply-To: <18730.23018.15596.789141@fencepost.gnu.org> (Glenn Morris's message of "Mon, 24 Nov 2008 02:38:18 -0500")
Glenn Morris <rgm@gnu.org> writes:
>> +2008-11-22 Glenn Morris <rgm@gnu.org>
>> +
>> + * vc-hg.el (vc-hg-program): New option.
>> + (vc-hg-state, vc-hg-working-revision, vc-hg-command):
>> + Use vc-hg-program rather than hard-coded "hg".
>>
>> Why was it done? Did any user request it?
>
> Yes.
>
> http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00286.html
Norman Gray wrote:
> > Within vc-hg.el, the "hg" command is hard-wired as that precise
> > string, rather than being configurable. This is awkward for me at
> > least, since I organise myself so that tools (potentially in
> > multiple different versions) are kept out of /usr/local and similar,
> > and paged in and out via per-shell adjustments to PATH. But that
> > means that hg typically isn't on the default path that emacs picks
> > up.
This exotic setup is probably not a reason to change vc-hg, especially
when there is no equivalent in the other VC backends. Maybe OP can come
up with a different way to do what he wants (e.g., advising the VC
functions to swap in the correct path).
next prev parent reply other threads:[~2008-11-24 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200811221752.mAMHqCqK020038@mothra.ics.uci.edu>
2008-11-24 7:38 ` your vc-hg.el change Glenn Morris
2008-11-24 9:31 ` Dan Nicolaescu
2008-11-24 17:18 ` Glenn Morris
2008-11-24 18:02 ` Chong Yidong
2008-11-24 15:52 ` Chong Yidong [this message]
2008-11-24 17:15 ` Glenn Morris
2008-11-24 18:01 ` Chong Yidong
2008-11-24 18:19 ` Glenn Morris
2008-11-25 1:59 ` Stephen J. Turnbull
2008-11-25 3:17 ` mail
2008-11-25 7:25 ` Stephen J. Turnbull
2009-01-12 10:36 Norman Gray
2010-11-17 14:36 ` Stefan Monnier
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=87od05azpk.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/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).