From: Eli Zaretskii <eliz@gnu.org>
To: ynyaaa@gmail.com
Cc: 38645@debbugs.gnu.org
Subject: bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown
Date: Tue, 17 Dec 2019 14:07:20 +0200 [thread overview]
Message-ID: <AED3082A-4538-41F1-B47A-8949425237DC@gnu.org> (raw)
In-Reply-To: <86o8w79nej.fsf@gmail.com>
On December 17, 2019 1:55:48 PM GMT+02:00, ynyaaa@gmail.com wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > On December 17, 2019 8:49:17 AM GMT+02:00, ynyaaa@gmail.com wrote:
> >>
>
> > That's a feature: by default the mini-window only grows
> automatically,
> > and doesn't get reset to its original 1 line until the echo area is
> > cleared. If you don't like this, customize resize-mini-windows to
> the
> > value t, or bind it temporarily while running code such as in the
> > recipe.
>
> This may happen with unrelated commands.
> Commands below shows an example.
> Please input M-x as one key event, not ESC x.
>
> M-: "1\n2" RET
> M-x
When I type this with resize-mini-windows set to t, typing M-x causes the mini-window to shrink back to its original one-line height. So I don't think I understand the complaint.
next prev parent reply other threads:[~2019-12-17 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 6:49 bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown ynyaaa
2019-12-17 7:41 ` Eli Zaretskii
2019-12-17 11:55 ` ynyaaa
2019-12-17 12:07 ` Eli Zaretskii [this message]
2019-12-18 10:52 ` ynyaaa
2019-12-18 16:31 ` Eli Zaretskii
2019-12-20 2:16 ` ynyaaa
2019-12-26 20:49 ` Eli Zaretskii
2019-12-27 9:12 ` martin rudalics
2019-12-27 9:21 ` Eli Zaretskii
2019-12-27 9:46 ` martin rudalics
2019-12-27 10:29 ` Eli Zaretskii
2019-12-29 14:15 ` Eli Zaretskii
2019-12-29 18:33 ` martin rudalics
2019-12-29 18:50 ` Eli Zaretskii
2019-12-29 19:30 ` martin rudalics
2019-12-30 16:07 ` Eli Zaretskii
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=AED3082A-4538-41F1-B47A-8949425237DC@gnu.org \
--to=eliz@gnu.org \
--cc=38645@debbugs.gnu.org \
--cc=ynyaaa@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 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.