From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 3465@debbugs.gnu.org, larsi@gnus.org, 4477@debbugs.gnu.org,
bojohan@gnu.org
Subject: bug#4477: bug#3465: 23.0.94; feature request: be able to log minibuffer messages
Date: Sat, 22 Aug 2020 20:02:53 +0300 [thread overview]
Message-ID: <834kouaa0y.fsf@gnu.org> (raw)
In-Reply-To: <f1623e09-ceee-4ba6-9cf2-205d292ee017@default> (message from Drew Adams on Sat, 22 Aug 2020 09:54:14 -0700 (PDT))
> Date: Sat, 22 Aug 2020 09:54:14 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 3465@debbugs.gnu.org, bojohan@gnu.org, 4477@debbugs.gnu.org
>
> > >> 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.
>
> No. The request is to _be able_ to also log
> `minibuffer-message' feedback.
>
> > > By default? I'd object to that. As an option, maybe;
>
> The bug requested to _be able to_ do it.
> Not to do it by default.
I was responding to Lars, not to your original request.
> > > 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.
>
> No. `minibuffer-message' has an entirely different
> UI effect. You are coupling the UI effect (messaging)
> with the logging effect. It is you, even in your "but
> then" (i.e., NOT by default), who are saying that
> every time logging is wanted the UI effect of `message'
> is also wanted.
Yes, yes, everyone knows that. No need to reiterate the trivia.
Please focus on the real issues at hand.
> That's exactly the point of this bug:
>
> 1. `message' and `minibuffer-message' have different UI
> effects. They are used for different things.
>
> 2. `message' can be logged. `minibuffer-message' cannot.
>
> The point is to be able to log `minibuffer-message',
> WITHOUT getting the different UI effect of `message'.
Yes, we understood that. No need to reiterate.
> Please reread the bug report. I don't think it's hard
> to understand the request: Be able to also log
> `minibuffer-message' output.
Please re-read what I responded. Which part of it contradicts what
you requested?
> And obviously WITHOUT calling `message', which is not
> logging `minibuffer-message' but logging `message',
> and which adds the UI effect of `message'.
The UI effect of 'message' can be easily disabled by the Lisp program
which calls 'message', which in effect converts 'message' into a
logging function. Include that in the code that calls
'minibuffer-message', and you have what you wanted, no?
> Eli seems to have clearly misunderstood the request.
Please don't second-guess my misunderstandings. It is rude, to say
the least.
> Please reopen this enhancement request. It's simply
> a request to _be able to_ log `minibuffer-message'
> output. Not a big deal.
You are already able to do that, AFAICT.
next prev parent reply other threads:[~2020-08-22 17:02 UTC|newest]
Thread overview: 22+ 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
2020-08-22 16:54 ` Drew Adams
2020-08-22 17:02 ` Eli Zaretskii [this message]
[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 ` bug#4477: " Drew Adams
2020-08-22 18:34 ` Lars Ingebrigtsen
2020-08-22 18:36 ` bug#4477: " Eli Zaretskii
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=834kouaa0y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3465@debbugs.gnu.org \
--cc=4477@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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.