From: Oleh Krehel <ohwoeowho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39564@debbugs.gnu.org
Subject: bug#39564: 28.0.50; read-key function do not display the prompt if called from read-from-minibuffer
Date: Wed, 12 Feb 2020 14:21:35 +0100 [thread overview]
Message-ID: <CAA01p3qye31Ad9VUvwgxpemhRyDgb0HcMxxK_Cn3=NNb15Ondg@mail.gmail.com> (raw)
In-Reply-To: <83y2t9qb51.fsf@gnu.org>
> Thanks, but I still don't understand what should one do with this
> snippet (after evaluating it) to see the problem. Please tell more.
Here's the behavior in 26.3: the minibuffer is 10 lines tall for
read-from-minibuffer. I'd like read-key to keep the same window height
as not to distract the user, and to have the whole contents of
read-key hint to take over the 10 lines of the minibuffer. Right now,
on 28, the hint is only partially visible. While the behavior on 26.3
and earlier is exactly what I want.
next prev parent reply other threads:[~2020-02-12 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200211144941.godmcifegapmqg6i.ref@Ergus>
2020-02-11 14:49 ` bug#39564: 28.0.50; read-key function do not display the prompt if called from read-from-minibuffer Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-02-11 15:50 ` Eli Zaretskii
2020-02-11 16:17 ` Oleh Krehel
2020-02-11 17:36 ` Eli Zaretskii
2020-02-12 13:21 ` Oleh Krehel [this message]
2020-02-12 17:22 ` Eli Zaretskii
2020-02-12 22:37 ` bug#39564: 28.0.50; read-key function do not display the prompt Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-02-26 20:04 ` bug#39564: Matt Kramer
2020-02-28 7:26 ` bug#39564: Eli Zaretskii
2020-02-28 17:33 ` bug#39564: Matt Kramer
2020-02-29 8:16 ` bug#39564: Eli Zaretskii
2020-03-01 22:26 ` bug#39564: Matt Kramer
2020-03-02 7:20 ` bug#39564: Matt Kramer
2020-03-02 8:46 ` bug#39564: Eli Zaretskii
2022-02-20 15:13 ` bug#39564: 28.0.50; read-key function do not display the prompt if called from read-from-minibuffer 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='CAA01p3qye31Ad9VUvwgxpemhRyDgb0HcMxxK_Cn3=NNb15Ondg@mail.gmail.com' \
--to=ohwoeowho@gmail.com \
--cc=39564@debbugs.gnu.org \
--cc=eliz@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).