From: Tino Calancha <f92capac@gmail.com>
To: 21663@debbugs.gnu.org
Subject: bug#21663: 25.0.50; isearch-edit-string dont resume multi-isearch-files
Date: Tue, 13 Oct 2015 00:25:12 +0900 (JST) [thread overview]
Message-ID: <alpine.LRH.2.20.1510130023130.12592@calancha-ilc.kek.jp> (raw)
In-Reply-To: <handler.21663.B.144453929427612.ack@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Previous patch would not work for `multi-isearch-files'
because it is not checking `multi-isearch-file-list', so that
`multi-isearch-end' would be called.
We may replace
(if (and nopush edit multi-isearch-buffer-list)
with
(if (and nopush edit (or multi-isearch-buffer-list multi-isearch-file-list))
but just
(if (and nopush edit)
wold work in any situation and its shorter.
[-- Attachment #2: Type: text/plain, Size: 705 bytes --]
gdiff --git a/lisp/isearch.el b/lisp/isearch.el
index 4fc9b38..6107bd5 100644
--- a/lisp/isearch.el
+++ b/lisp/isearch.el
@@ -1086,7 +1086,10 @@ isearch-done
;; Update the ring data.
(isearch-update-ring isearch-string isearch-regexp))
- (let ((isearch-mode-end-hook-quit (and nopush (not edit))))
+ (let ((isearch-mode-end-hook-quit (and nopush (not edit)))
+ (isearch-mode-end-hook (if (and nopush edit)
+ (delq 'multi-isearch-end isearch-mode-end-hook)
+ isearch-mode-end-hook)))
(run-hooks 'isearch-mode-end-hook))
;; If there was movement, mark the starting position.
next prev parent reply other threads:[~2015-10-12 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 4:57 bug#21663: Subject: 25.0.50; isearch-edit-string dont resume multi isearches Tino Calancha
[not found] ` <handler.21663.B.144453929427612.ack@debbugs.gnu.org>
2015-10-12 15:25 ` Tino Calancha [this message]
2015-10-12 20:17 ` bug#21663: 25.0.50; isearch-edit-string dont resume multi-isearch-files Juri Linkov
2015-10-13 1:35 ` Tino Calancha
2015-10-13 5:18 ` bug#21663: 25.0.50; isearch-edit-string dont resume multi isearches Tino Calancha
2015-10-13 22:04 ` Juri Linkov
2015-10-14 6:48 ` Tino Calancha
2015-10-14 16:17 ` Juri Linkov
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.1510130023130.12592@calancha-ilc.kek.jp \
--to=f92capac@gmail.com \
--cc=21663@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 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.