From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60015@debbugs.gnu.org
Subject: bug#60015: 29.0.60; multi-line messages truncated in non-selected minibuffer
Date: Tue, 13 Dec 2022 19:20:06 +0200 [thread overview]
Message-ID: <865yefw7o5.fsf@mail.linkov.net> (raw)
In-Reply-To: <83a63sqvhq.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Dec 2022 21:20:49 +0200")
>> >> 1. (run-with-timer 5 5 'message "abc\ndef")
>> >> 2. then activate the minibuffer and switch back to the original buffer
>> >> 3. after some time observe that only the first line of the multi-line message
>> >> is displayed in the minibuffer
>> >
>> > Doesn't happen here (I waited for 2.5 minutes). Is the recipe
>> > complete and exact? Does it perhaps matter how do you "switch back to
>> > the original buffer"? (I used a mouse click.)
>>
>> It's essential to ensure that the height of the minibuffer/echo area
>> initially is not more than 1 line.
>
> That's so by default, so "emacs -Q" should ensure that. Right?
Evaluating the first line above resizes the minibuffer,
and the timer resizes the minibuffer, so it's difficult
to find a moment when it's exactly 1 line high.
I have no idea how to simplify this test case.
>> > When the problem happens, what do you see in *Messages*? Anything
>> > other that "abc\ndef"?
>>
>> Only the first line "abc" is displayed in the minibuffer
>> as the minibuffer message.
>
> I asked about the *Messages* buffer, not about the minibuffer.
Sorry. The *Messages* buffer shows all lines of the multi-line string.
next prev parent reply other threads:[~2022-12-13 17:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 18:03 bug#60015: 29.0.60; multi-line messages truncated in non-selected minibuffer Juri Linkov
2022-12-12 18:19 ` Eli Zaretskii
2022-12-12 18:37 ` Juri Linkov
2022-12-12 19:20 ` Eli Zaretskii
2022-12-13 17:20 ` Juri Linkov [this message]
2022-12-13 17:44 ` Eli Zaretskii
2022-12-13 17:56 ` Juri Linkov
2022-12-15 7:44 ` Juri Linkov
2022-12-15 10:18 ` martin rudalics
2022-12-15 13:36 ` Eli Zaretskii
2022-12-15 14:30 ` Eli Zaretskii
2022-12-15 15:07 ` martin rudalics
2022-12-15 15:12 ` martin rudalics
2022-12-15 15:30 ` Eli Zaretskii
2022-12-15 17:35 ` Juri Linkov
2022-12-17 17:39 ` Juri Linkov
2022-12-17 18:45 ` Eli Zaretskii
2022-12-15 16:44 ` Gregory Heytings
2022-12-15 17:03 ` Eli Zaretskii
2022-12-15 17:37 ` Juri Linkov
2022-12-15 21:52 ` Gregory Heytings
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=865yefw7o5.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=60015@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).