From: Richard Stallman <rms@gnu.org>
To: esr@thyrsus.com
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: vc-diff in non-VC buffer
Date: Sat, 13 Oct 2007 02:40:22 -0400 [thread overview]
Message-ID: <E1Igafe-0001I2-OT@fencepost.gnu.org> (raw)
In-Reply-To: <20071011120005.GD6804@thyrsus.com> (esr@thyrsus.com)
Yes. For that particular operation, and some other non-modifying ones
such as printing change-history logs, what users often want is a
fallback rule for computing selected filesets that says, in effect:
if the selected fileset is empty, look at all version-controlled
files beneath the current directory.
Is that really the right condition? I think it is not quite right.
I do not want it to search your tree when that is not wanted.
I'm testing code that errors out if you (a) have an empty fileset, and
(b) no files are registered immediately under default-directory. Juanma
thinks this will cover his use case.
What will this do in the original case:
you visit a file in your home dir and tyoe C-x v =.
In that case, do you have a nonempty fileset?
If so, it sounds like the criterion for the error
would not be met, and it would search your whole tree.
prev parent reply other threads:[~2007-10-13 6:40 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Igafe-0001I2-OT@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.