From: Tino Calancha <f92capac@gmail.com>
To: kifer@cs.stonybrook.edu, 21852@debbugs.gnu.org
Cc: Tino Calancha <f92capac@gmail.com>
Subject: bug#21852: Ediff 2.81.5 of July 4, 2013; ediff-patch-buffer fails if patch-buf doesn't exists.
Date: Sun, 8 Nov 2015 00:21:54 +0900 (JST) [thread overview]
Message-ID: <alpine.LRH.2.20.1511080019460.11665@calancha-ilc.kek.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Congratulations! You may have unearthed a bug in Ediff!
Please make a concise and accurate summary of what happened
and mail it to the address above.
-----------------------------------------------------------
ediff-patch-buffer fails if patch-buf doesn't exists.
* lisp/vc/ediff.el (ediff-patch-buffer): Added 'require-match
argument on read-buffer call.
emacs -Q:
(in the *scratch* buffer)
(with-current-buffer (generate-new-buffer "buff")
(insert "foo bar"))
(with-current-buffer (generate-new-buffer "buff2")
(insert "foo baz"))
;; call ediff-buffers on "buff" and "buff2" and save the
;; differences in a buffer "patch"
M-x epatch-buffer y patch RET buff ; ok
M-x epatch-buffer y patch RET buffer ; BAD
You have killed a vital Ediff buffer---you must leave Ediff now!
Emacs : GNU Emacs 25.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.28)
of 2015-11-07
Package: Ediff 2.81.5 of July 4, 2013
[-- Attachment #2: Type: text/plain, Size: 354 bytes --]
diff --git a/lisp/vc/ediff.el b/lisp/vc/ediff.el
index 3a2d1e4..8723c19 100644
--- a/lisp/vc/ediff.el
+++ b/lisp/vc/ediff.el
@@ -1403,7 +1403,7 @@ ediff-patch-buffer
patch-buf
(read-buffer
"Which buffer to patch? "
- (ediff-other-buffer patch-buf))))
+ (ediff-other-buffer patch-buf) 'require-match)))
;;;###autoload
next reply other threads:[~2015-11-07 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 15:21 Tino Calancha [this message]
2016-02-23 5:04 ` bug#21852: Ediff 2.81.5 of July 4, 2013; ediff-patch-buffer fails if patch-buf doesn't exists 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.20.1511080019460.11665@calancha-ilc.kek.jp \
--to=f92capac@gmail.com \
--cc=21852@debbugs.gnu.org \
--cc=kifer@cs.stonybrook.edu \
/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.