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 15:42:24 +0300 [thread overview]
Message-ID: <83blhgdetr.fsf@gnu.org> (raw)
In-Reply-To: <112871601882593@mail.yandex.ru> (message from pinkanon pinkanon on Mon, 05 Oct 2020 10:34:49 +0300)
> From: pinkanon pinkanon <pinkanon.pinkanon@yandex.com>
> Date: Mon, 05 Oct 2020 10:34:49 +0300
>
> Eval this:
>
> (progn (minibuffer-message "hello world") (print (format "current message: %s" (current-message))))
>
> to get "current message: nil" in the *Messages*. If message is used in place of minibuffer message, works
> as expected.
I think your expectations are incorrect, and Emacs works correctly in
this case.
> The reason I think current-message should work with minibuffer-message is due to its docstring: "Return the
> string currently displayed in the echo area, or nil if none."
The echo area and the minibuffer are two different buffers. They both
use the same mini-window to display their text, but they are not the
same.
> PS Is there some other way to get what's currently displayed in the echo area?
You mean, what is shown in the mini-window? Is minibuffer-contents
what you want?
next prev parent reply other threads:[~2020-10-05 12:42 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 [this message]
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
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
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=83blhgdetr.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 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).