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: Mon, 05 Oct 2020 21:19:10 +0300 [thread overview]
Message-ID: <831riccz8h.fsf@gnu.org> (raw)
In-Reply-To: <589651601919337@mail.yandex.ru> (message from pinkanon pinkanon on Mon, 05 Oct 2020 20:43:33 +0300)
> From: pinkanon pinkanon <pinkanon.pinkanon@yandex.com>
> Cc: "43813@debbugs.gnu.org" <43813@debbugs.gnu.org>
> Date: Mon, 05 Oct 2020 20:43:33 +0300
>
> I am doing an eldoc sort of thing and I don't want my hint messages interfering with any other, probably more
> important, messages. I want to do it by seeing if there's anything at all displayed currently in the mini window
> and, if not, show my hint. I guess current-message should meet most of my needs, but I got curious and
> asked anyhow.
If the minibuffer is active (i.e. the user is typing a response for
some prompt), the hints you show via 'message' will not overwrite the
minibuffer stuff, but will be shown after it. So you should have no
problems due to minibuffer editing in your application.
next prev parent reply other threads:[~2020-10-05 18: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 [this message]
2020-10-06 7:52 ` pinkanon pinkanon
2020-10-06 8:19 ` Eli Zaretskii
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=831riccz8h.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.