From: David Kastrup <dak@gnu.org>
To: esr@thyrsus.com
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>,
Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org
Subject: Re: vc-directory breakage
Date: Tue, 06 May 2008 08:36:55 +0200 [thread overview]
Message-ID: <85y76o546w.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20080506004849.GA14523@thyrsus.com> (Eric S. Raymond's message of "Mon, 5 May 2008 20:48:49 -0400")
"Eric S. Raymond" <esr@thyrsus.com> writes:
> The recommended change may be a good idea, but I'm not sure. Those
> backend checks are now being done at file granularity because some
> people were vocal about support for mixing multiple VCSes in a
> directory. If we depended on a per-directory buffer-local variable,
> that would get more difficult.
Not at all. The buffer-local variable is just used for starting off the
directory in the right mode and keeping it there.
The question one needs to solve is what to do when a command would reuse
*vc-dir* and would have an idea gained from the buffer where the command
has been issued just what backend *vc-dir* should be using, and *vc-dir*
is actually different.
There are two solutions I see for that: it could scrap the existing
buffer completely, or it could get-buffer-create *vc-dir*<backend> (with
the proper backend spelled out in the brackets). If the normal mode of
operation would scrap the buffer too without leaving existing
information in it, that would be the obvious choice.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2008-05-06 6:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 15:21 vc-directory breakage Eric S. Raymond
2008-05-05 15:32 ` David Kastrup
2008-05-05 15:39 ` Bastien Guerry
2008-05-05 15:45 ` David Kastrup
2008-05-05 15:52 ` Juanma Barranquero
2008-05-05 16:03 ` David Kastrup
2008-05-05 16:23 ` Bastien Guerry
2008-05-05 16:40 ` David Kastrup
2008-05-05 16:50 ` Lennart Borgman (gmail)
2008-05-05 17:00 ` Bastien Guerry
2008-05-05 20:14 ` Juanma Barranquero
2008-05-05 22:09 ` Thomas Lord
2008-05-05 22:17 ` Stephen J. Turnbull
2008-05-06 0:04 ` Eric S. Raymond
2008-05-06 0:36 ` Dan Nicolaescu
2008-05-06 0:48 ` Eric S. Raymond
2008-05-06 1:03 ` Stefan Monnier
2008-05-06 8:21 ` Eric S. Raymond
2008-05-06 9:08 ` David Kastrup
2008-05-06 16:34 ` Dan Nicolaescu
2008-05-07 1:30 ` Stefan Monnier
2008-05-06 1:10 ` Dan Nicolaescu
2008-05-06 9:01 ` Eric S. Raymond
2008-05-06 12:03 ` Dan Nicolaescu
2008-05-06 16:03 ` Eric S. Raymond
2008-05-06 6:36 ` David Kastrup [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=85y76o546w.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.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).