unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Oleh Krehel <ohwoeowho@gmail.com>
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 19:22:07 +0200	[thread overview]
Message-ID: <83tv3vra9s.fsf@gnu.org> (raw)
In-Reply-To: <CAA01p3qye31Ad9VUvwgxpemhRyDgb0HcMxxK_Cn3=NNb15Ondg@mail.gmail.com> (message from Oleh Krehel on Wed, 12 Feb 2020 14:21:35 +0100)

> From: Oleh Krehel <ohwoeowho@gmail.com>
> Date: Wed, 12 Feb 2020 14:21:35 +0100
> Cc: 39564@debbugs.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.

Sorry, I still don't understand: are you saying that you get a 10-line
mini-window after just evaluating the code snippet you posted?  If so,
then I cannot reproduce that: I see a 9-line mini-window, both in
Emacs 26.3 and the current emacs-27 branch (Emacs 27.0.60).

Do I need to do anything after evaluating the code you posted?  (I
think I do, because otherwise I don't understand, for example, why you
bind C-f to some function there.)

Thanks.





  reply	other threads:[~2020-02-12 17:22 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
2020-02-12 17:22         ` Eli Zaretskii [this message]
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=83tv3vra9s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39564@debbugs.gnu.org \
    --cc=ohwoeowho@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).