From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: basil@contovou.net, stephen.berman@gmx.net,
71927@debbugs.gnu.org, kickingvegas@gmail.com, juri@linkov.net
Subject: bug#71927: 29.4; ibuffer-do-isearch and ibuffer-do-isearch-regexp not prompting for input
Date: Fri, 12 Jul 2024 12:20:01 +0200 [thread overview]
Message-ID: <m1zfqmx67i.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <86r0bzks7c.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Jul 2024 10:03:19 +0300")
close 71927 30.1
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eshel Yaron <me@eshelyaron.com>
>>
>> Actually, there's another problem with the way ibuffer-do-isearch is
>> currently defined via define-ibuffer-op: the BODY of the definition is a
>> call to multi-isearch-buffers, but the BODY is called for each marked
>> buffer, not once for all of them, so this command currently calls
>> multi-isearch-buffers repeatedly when there are multiple marked buffers.
>> This causes multi-isearch-setup to be called while multi-buffer Isearch
>> is already in progress, which unfortunately breaks regular Isearch for
>> the rest of the session.
>>
>> To see this effect, invoke ibuffer-do-isearch with two or more marked
>> buffers, quit or finish the search (e.g. type C-g), and then try regular
>> Isearch with C-s and repeat C-s until wrapping around. But instead of
>> wrapping around as expected, Emacs displays an error:
>>
>> Symbol’s function definition is void: nil
>>
>> A simple solution is to use plain defun for these commands, as follows:
>
> Thanks. Since there were no objections in a week, and Juri also
> agreed with this solution, please install this on the emacs-30 branch.
Done, in commit d68a4ea3ec6. I'm therefore closing this bug report.
Best,
Eshel
next prev parent reply other threads:[~2024-07-12 10:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 21:25 bug#71927: 29.4; ibuffer-do-isearch and ibuffer-do-isearch-regexp not prompting for input Charles Choi
2024-07-04 6:58 ` Juri Linkov
2024-07-04 7:55 ` Eli Zaretskii
2024-07-04 7:12 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-04 9:59 ` Eli Zaretskii
2024-07-04 10:06 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-04 12:50 ` Eli Zaretskii
2024-07-04 13:32 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-04 14:12 ` Eli Zaretskii
2024-07-04 15:09 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-04 16:04 ` Juri Linkov
2024-07-04 17:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-04 18:07 ` Eli Zaretskii
2024-07-04 18:29 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-04 18:46 ` Eli Zaretskii
2024-07-06 21:13 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-07 16:59 ` Juri Linkov
2024-07-12 7:03 ` Eli Zaretskii
2024-07-12 10:20 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-12 17:05 ` Charles Choi
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=m1zfqmx67i.fsf@dazzs-mbp.home \
--to=bug-gnu-emacs@gnu.org \
--cc=71927@debbugs.gnu.org \
--cc=basil@contovou.net \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=kickingvegas@gmail.com \
--cc=me@eshelyaron.com \
--cc=stephen.berman@gmx.net \
/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.