From: Stefan Kangas <stefan@marxist.se>
To: Brent Goodrick <bgoodr@gmail.com>
Cc: 5584@debbugs.gnu.org
Subject: bug#5584: 23.1.90; Setting enable-recursive-minibuffers to non-nil ignores minibuffer history
Date: Wed, 23 Oct 2019 13:23:56 +0200 [thread overview]
Message-ID: <CADwFkmmDGL6UuLngjAgt3itOmt_5ZAKOheqT5j_60pqeNNQ1OA@mail.gmail.com> (raw)
In-Reply-To: <19322.45565.449246.364467@gargle.gargle.HOWL>
found 5584 27.0.50
tags 5584 + confirmed
quit
Brent Goodrick <bgoodr@gmail.com> writes:
> Starting from `emacs -Q' off of a freshly built Emacs from CVS on a
> 32-bit RHEL5 system (but the system doesn't matter since I've seen this
> on Windows and 64-bit Linux):
>
> 1. Switch into the *scratch* buffer
> 2. Type the following:
> (setq enable-recursive-minibuffers t)
> Hit Control-J to evaluate it
> 3. Type M-x flush-lines RET
> 4. While the minibuffer is active waiting for the string for
> `flush-lines', type M-: (or its equivalent of `M-x eval-expression')
> 5. Type (insert "flubber") RET
> 6. Type RET to complete the flush-lines
> 7. Do steps 3 and 4 again.
> 8. Type M-p and notice the error message stating no previous history element,
> which is incorrect.
I can reproduce this on the current master branch.
> The reason this is an issue is that I find myself constantly needing
> to type in a regular expression using `rx' syntax via
>
> (insert (rx ....))
>
> and not being able to get back to that history element is a burden for
> complex rx expressions. Not using `' seems to fix it, but then I give
> up recursive minibuffers which I find very handy.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-10-23 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 14:55 bug#5584: 23.1.90; Setting enable-recursive-minibuffers to non-nil ignores minibuffer history Brent Goodrick
2019-10-23 11:23 ` Stefan Kangas [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
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=CADwFkmmDGL6UuLngjAgt3itOmt_5ZAKOheqT5j_60pqeNNQ1OA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=5584@debbugs.gnu.org \
--cc=bgoodr@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 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).