From: Eli Zaretskii <eliz@gnu.org>
To: pinkanon pinkanon <pinkanon.pinkanon@yandex.com>
Cc: 43813@debbugs.gnu.org
Subject: bug#43813: [BUG] current-message not working with minibuffer-message
Date: Tue, 06 Oct 2020 11:19:50 +0300 [thread overview]
Message-ID: <83blhfbwbd.fsf@gnu.org> (raw)
In-Reply-To: <81711601970284@mail.yandex.ru> (message from pinkanon pinkanon on Tue, 06 Oct 2020 10:52:23 +0300)
> From: pinkanon pinkanon <pinkanon.pinkanon@yandex.com>
> Cc: "43813@debbugs.gnu.org" <43813@debbugs.gnu.org>
> Date: Tue, 06 Oct 2020 10:52:23 +0300
>
> It's not only minibuffer editing though. It could be just regular messages/minibuffer-messages from anywhere
> else. For instance messages from a linter or some callback response from some connection letting you
> know something's been set up. I don't want my low-priority hinting covering any of that up.
The messages displayed by minibuffer-message will always disappear
after the timeout, or when some input event arrives. So they cannot
be a problem in your application, I think.
If you do see some problems, could you show some simple example of
that?
next prev parent reply other threads:[~2020-10-06 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 7:34 bug#43813: [BUG] current-message not working with minibuffer-message pinkanon pinkanon
2020-10-05 12:42 ` Eli Zaretskii
2020-10-05 15:56 ` pinkanon pinkanon
2020-10-05 16:05 ` pinkanon pinkanon
2020-10-05 16:08 ` Eli Zaretskii
2020-10-05 16:33 ` pinkanon pinkanon
2020-10-05 17:01 ` Eli Zaretskii
2020-10-05 17:43 ` pinkanon pinkanon
2020-10-05 18:19 ` Eli Zaretskii
2020-10-06 7:52 ` pinkanon pinkanon
2020-10-06 8:19 ` Eli Zaretskii [this message]
2020-10-06 8:46 ` pinkanon pinkanon
2020-10-06 9:04 ` Eli Zaretskii
2020-10-06 11:01 ` pinkanon pinkanon
2020-10-06 11:06 ` Eli Zaretskii
2020-10-06 13:39 ` pinkanon pinkanon
2020-10-07 3:06 ` Lars Ingebrigtsen
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=83blhfbwbd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43813@debbugs.gnu.org \
--cc=pinkanon.pinkanon@yandex.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.