From: "Eric S. Raymond" <esr@thyrsus.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: vc-diff in non-VC buffer
Date: Wed, 10 Oct 2007 18:13:41 -0400 [thread overview]
Message-ID: <20071010221340.GA1578@thyrsus.com> (raw)
In-Reply-To: <f7ccd24b0710101458x2fa52061sb5e9d9d3837cbef2@mail.gmail.com>
Juanma Barranquero <lekktu@gmail.com>:
> I'm not saying my view is the only one reasonable, but to me the
> current behavior is a regression.
I hear that. Let's try to think about smarter ways for the code to behave.
> > I think people are likely to become quite upset with me if I
> > remove that.
>
> Then at the very least make it a user option, please.
I'd rather not. Doing the right thing is better than options, when
you can figure out what it is. And too often, adding options becomes
an excuse not to figure that out.
How about this: VC can test whether some VCS considers itself responsible
for a directory. I could change the logic to error out when no VCS considers
itself responsible for the current directory. Would that cover your
use case?
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2007-10-10 22:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 17:19 vc-diff in non-VC buffer Juanma Barranquero
2007-10-10 17:38 ` Eric S. Raymond
2007-10-10 21:31 ` Juanma Barranquero
2007-10-10 21:49 ` Eric S. Raymond
2007-10-10 21:58 ` Juanma Barranquero
2007-10-10 22:13 ` Eric S. Raymond [this message]
2007-10-10 22:23 ` Juanma Barranquero
2007-10-10 22:57 ` Eric S. Raymond
2007-10-10 23:06 ` Juanma Barranquero
2007-10-14 16:29 ` Richard Stallman
2007-10-10 22:30 ` Andreas Schwab
2007-10-10 22:57 ` Eric S. Raymond
2007-10-11 5:20 ` Richard Stallman
2007-10-11 12:00 ` Eric S. Raymond
2007-10-11 14:39 ` Stefan Monnier
2007-10-11 17:40 ` Richard Stallman
2007-10-13 6:40 ` Richard Stallman
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=20071010221340.GA1578@thyrsus.com \
--to=esr@thyrsus.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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).