From: Phil Sainty <psainty@orcon.net.nz>
To: 38575@debbugs.gnu.org
Subject: bug#38575: 27.0.50; Document that `diff' arguments OLD and NEW can be buffers
Date: Thu, 12 Dec 2019 20:44:15 +1300 [thread overview]
Message-ID: <5ce9330b0930c6a72c26fd08f66156d4@webmail.orcon.net.nz> (raw)
In-Reply-To: <d770eebbe9929e2842cd8592780440ad@webmail.orcon.net.nz>
This feature dates to the following commit, which I believe was
first released in 24.1.
Because this seems such a useful feature, I'm inclined to add a
NEWS entry as well, with the note "This change was made in Emacs
24.1, but wasn't documented until now."
-Phil
commit b2e4481906ec08e2c6072b6fe14dd1efca4784b9
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Mon Nov 22 14:22:03 2010 -0500
Cleanup diff-buffer-with-file.
* lisp/vc/diff.el (diff-old-temp-file, diff-new-temp-file): Remove.
(diff-sentinel): Get them as arguments instead.
(diff-old-file, diff-new-file, diff-extra-args): Remove.
(diff-file-local-copy, diff-better-file-name): New funs.
(diff-no-select): Rename from diff-into-buffer.
Support buffers additionally to files. Move `buf' arg. Don't
display buf.
Prefer closures to buffer-local variables.
(diff): Adjust accordingly.
(diff-buffer-with-file): Move from files.el.
* lisp/files.el (diff-buffer-with-file): Move to vc/diff.el.
(diff-buffer-internal): Remove.
(diff-buffer-buffer): Remove.
(save-some-buffers-action-alist): Use diff-no-select so as not to
guess
the buffer name used, and so as not to mess up windows and frames.
next prev parent reply other threads:[~2019-12-12 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 6:46 bug#38575: 27.0.50; Document that `diff' arguments OLD and NEW can be buffers Phil Sainty
2019-12-12 7:44 ` Phil Sainty [this message]
2019-12-12 9:23 ` Eli Zaretskii
2019-12-12 9:21 ` Eli Zaretskii
2019-12-12 10:15 ` Phil Sainty
2019-12-12 11:35 ` Eli Zaretskii
2019-12-14 8:22 ` Phil Sainty
2019-12-14 9:03 ` Eli Zaretskii
2020-08-21 15:01 ` Lars Ingebrigtsen
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=5ce9330b0930c6a72c26fd08f66156d4@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=38575@debbugs.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).