From: Platon Pronko <platon7pronko@gmail.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Is there a way to avoid clobbering minibuffer by messages?
Date: Fri, 31 Mar 2023 15:10:42 +0800 [thread overview]
Message-ID: <e1a6583b-d5ba-f49a-7d5d-8e4b947c1bd6@gmail.com> (raw)
In-Reply-To: <58158ae4986f49e1690e@heytings.org>
On 2023-03-31 15:01, Gregory Heytings wrote:
>
>>> Actually no, I don't think I would want to put messages into the modeline. As I understand it I have multiple modelines on my screen - one for each window, and that would be unnecessary duplication of information.
>>
>> Did you even try the code? The message appears only in the modeline of the bottom window in the frame, right above the minibuffer.
>>
>
> (And it appears in the modeline only when the mini-buffer is active.)
>
I didn't try it out thoroughly, sorry. I saw that it appeared in minibuffer as usual and decided to not look into it further.
I think of modeline as something buffer-specific, so I don't want to put global messages there.
Regarding your code - I might be wrong, but won't message get stuck in the modeline if I reorder my windows before the timer runs out?
--
Best regards,
Platon Pronko
PGP 2A62D77A7A2CB94E
next prev parent reply other threads:[~2023-03-31 7:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 7:57 Is there a way to avoid clobbering minibuffer by messages? Platon Pronko
2023-03-30 8:53 ` Eli Zaretskii
2023-03-30 9:40 ` Platon Pronko
2023-03-30 10:32 ` Eli Zaretskii
2023-03-30 15:05 ` Gregory Heytings
2023-03-30 16:28 ` [External] : " Drew Adams
2023-03-30 16:35 ` Eli Zaretskii
2023-03-30 16:49 ` Drew Adams
2023-03-30 17:27 ` Eli Zaretskii
2023-03-30 17:32 ` Gregory Heytings
2023-03-30 17:51 ` Eli Zaretskii
2023-03-30 18:14 ` John Yates
2023-03-30 18:28 ` Eli Zaretskii
2023-03-30 20:08 ` John Yates
2023-03-31 6:32 ` Yuri Khan
2023-03-30 18:16 ` Gregory Heytings
2023-03-30 18:31 ` Eli Zaretskii
2023-03-30 19:37 ` Sergey Organov
2023-03-30 19:45 ` Gregory Heytings
2023-03-30 20:02 ` Gregory Heytings
2023-03-30 20:06 ` Gregory Heytings
2023-03-30 19:26 ` Jean Louis
2023-03-31 10:40 ` Eric S Fraga
2023-03-30 19:22 ` Jean Louis
2023-03-31 6:24 ` Platon Pronko
2023-03-31 6:58 ` Gregory Heytings
2023-03-31 7:01 ` Gregory Heytings
2023-03-31 7:10 ` Platon Pronko [this message]
2023-03-31 7:17 ` Gregory Heytings
2023-03-31 7:45 ` Gregory Heytings
2023-03-31 11:04 ` John Covici
2023-03-31 11:09 ` Gregory Heytings
2023-03-31 12:46 ` John Covici
2023-03-30 9: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=e1a6583b-d5ba-f49a-7d5d-8e4b947c1bd6@gmail.com \
--to=platon7pronko@gmail.com \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=help-gnu-emacs@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.
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).