From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 3465@debbugs.gnu.org, bojohan@gnu.org
Subject: bug#3465: 23.0.94; feature request: be able to log minibuffer messages
Date: Sat, 22 Aug 2020 15:49:56 +0200 [thread overview]
Message-ID: <87ft8en62j.fsf@gnus.org> (raw)
In-Reply-To: <83tuwv9mm2.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Aug 2020 10:16:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> There's no problem with logging in general. The request is to also have
>> the messages output by the minibuffer-message function also end up in
>> the *Messages* buffer.
>
> By default? I'd object to that. As an option, maybe; but then I
> don't understand why this is requested as a core feature, since any
> Lisp program that wants this can simply call 'message' with the same
> string, and be done.
I thought it would make sense to have that function behave as regularly
as possible...
However, looking at the use cases for minibuffer-message, all of the
in-tree calls are trivial: "Confirm". "Incomplete". "Hit space to
flush". All of those things are UI details that would be surprising to
have land in the *Messages* buffer.
So I agree with Eli, and I don't think this is something that
minibuffer-message should do at all. If something wants to do a
minibuffer-message and log it, then that thing should just do both.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-22 13:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:38 bug#3465: 23.0.94; feature request: be able to log minibuffer messages Drew Adams
2016-04-27 19:13 ` Lars Ingebrigtsen
2016-04-27 19:35 ` Drew Adams
2016-04-27 20:20 ` Johan Bockgård
2016-04-27 20:25 ` Lars Ingebrigtsen
2016-04-27 20:26 ` Lars Ingebrigtsen
2020-08-20 18:52 ` Lars Ingebrigtsen
2020-08-20 19:14 ` Eli Zaretskii
2020-08-20 19:18 ` Lars Ingebrigtsen
2020-08-20 19:41 ` Eli Zaretskii
2020-08-20 19:45 ` Lars Ingebrigtsen
2020-08-20 19:52 ` Eli Zaretskii
2020-08-20 20:03 ` Lars Ingebrigtsen
2020-08-20 23:40 ` Juri Linkov
2020-08-21 0:05 ` Lars Ingebrigtsen
2020-08-22 7:16 ` Eli Zaretskii
2020-08-22 13:49 ` Lars Ingebrigtsen [this message]
2020-08-22 16:54 ` Drew Adams
2020-08-22 17:02 ` bug#4477: " Eli Zaretskii
[not found] <<CE526A71768043CA82AE63F6386B70E7@us.oracle.com>
[not found] ` <<87a8keeufp.fsf@gnus.org>
[not found] ` <<87r3dq248n.fsf@gnu.org>
[not found] ` <<87ziseu7bh.fsf@gnus.org>
[not found] ` <<87zh6pkv4b.fsf@gnus.org>
[not found] ` <<83364hceou.fsf@gnu.org>
[not found] ` <<87k0xtktxc.fsf@gnus.org>
[not found] ` <<83wo1taywj.fsf@gnu.org>
[not found] ` <<871rk1ksob.fsf@gnus.org>
[not found] ` <<83sgchaydm.fsf@gnu.org>
[not found] ` <<87sgchjd9r.fsf@gnus.org>
[not found] ` <<83tuwv9mm2.fsf@gnu.org>
[not found] ` <<87ft8en62j.fsf@gnus.org>
[not found] ` <<f1623e09-ceee-4ba6-9cf2-205d292ee017@default>
[not found] ` <<834kouaa0y.fsf@gnu.org>
2020-08-22 18:11 ` Drew Adams
2020-08-22 18:34 ` Lars Ingebrigtsen
2020-08-22 18:36 ` bug#4477: " Eli Zaretskii
[not found] <<<CE526A71768043CA82AE63F6386B70E7@us.oracle.com>
[not found] ` <<<87a8keeufp.fsf@gnus.org>
[not found] ` <<<87r3dq248n.fsf@gnu.org>
[not found] ` <<<87ziseu7bh.fsf@gnus.org>
[not found] ` <<<87zh6pkv4b.fsf@gnus.org>
[not found] ` <<<83364hceou.fsf@gnu.org>
[not found] ` <<<87k0xtktxc.fsf@gnus.org>
[not found] ` <<<83wo1taywj.fsf@gnu.org>
[not found] ` <<<871rk1ksob.fsf@gnus.org>
[not found] ` <<<83sgchaydm.fsf@gnu.org>
[not found] ` <<<87sgchjd9r.fsf@gnus.org>
[not found] ` <<<83tuwv9mm2.fsf@gnu.org>
[not found] ` <<<87ft8en62j.fsf@gnus.org>
[not found] ` <<<f1623e09-ceee-4ba6-9cf2-205d292ee017@default>
[not found] ` <<<834kouaa0y.fsf@gnu.org>
[not found] ` <<028c363a-e801-4c9a-8ebd-d55180961cf7@default>
[not found] ` <<83zh6m8r4e.fsf@gnu.org>
2020-08-22 19:17 ` Drew Adams
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=87ft8en62j.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=3465@debbugs.gnu.org \
--cc=bojohan@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 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.