From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, 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: Fri, 27 Dec 2019 10:12:33 +0100 [thread overview]
Message-ID: <e994a9d1-8f20-5599-b94c-42a02bcb28ce@gmx.at> (raw)
In-Reply-To: <831rsqrevq.fsf@gnu.org>
> Martin, what do you think about the following fix? Is it correct, and
> if so, safe enough for the release branch?
It seems "correct" in the sense that our doc of 'resize-mini-windows'
nowhere contradicts any such interpretation. It should be "safe" in
the sense that failing to always resize the minibuffer window exactly
and falling back on 'grow-only' should not do any harm since otherwise
we'd have a bug in the 'grow-only' part of the code.
But I'm too silly to understand why the minibuffer window does not
re-grow in the first place after having shown the result of C-x C-e.
Can you enlighten me?
martin, who just noted that the recently added (to master)
Lisp_Object str = build_string ("Command attempted to use minibuffer"
"while in minibuffer");
produces
"Command attempted to use minibufferwhile in minibuffer"
martin
next prev parent reply other threads:[~2019-12-27 9:12 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
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 [this message]
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=e994a9d1-8f20-5599-b94c-42a02bcb28ce@gmx.at \
--to=rudalics@gmx.at \
--cc=38645@debbugs.gnu.org \
--cc=eliz@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.