From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ynyaaa@gmail.com, 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:46:57 +0100 [thread overview]
Message-ID: <f1bdec72-3091-1ba0-dcd6-641afecde81b@gmx.at> (raw)
In-Reply-To: <83o8vup1hk.fsf@gnu.org>
>> 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?
>
> Re-grow upon which event? If you do nothing, the message from "C-x C-e"
> stays displayed indefinitely.
Not here. After a short pause I get the one line ?a back.
> If you mean why it doesn't re-grow upon some keystroke (which removes
> the message), I guess we are lacking a call to
> resize_echo_area_exactly in some place.
I guess so too.
> Regardless, I think keeping the prompt visible is a better behavior.
But while showing the result of C-x C-e (97 ...) it doesn't show any
prompt here, just an empty trailing line. What am I missing?
> And yes, we should probably document this caveat, although I cannot
> imagine what application would like the current behavior.
>
>> 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"
>
> Hope you've already fixed it.
I cannot reliably push these days. I have to first rebuild my git
environment and probably will wait with that until Glen has fixed the
copyright headers to avoid excessive re-compilations. My machine is
getting a bit weak for so much work ...
martin
next prev parent reply other threads:[~2019-12-27 9:46 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
2019-12-27 9:21 ` Eli Zaretskii
2019-12-27 9:46 ` martin rudalics [this message]
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
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=f1bdec72-3091-1ba0-dcd6-641afecde81b@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 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).