From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, 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 11:11:23 -0700 (PDT) [thread overview]
Message-ID: <028c363a-e801-4c9a-8ebd-d55180961cf7@default> (raw)
In-Reply-To: <<834kouaa0y.fsf@gnu.org>>
> > 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?
Please read what you just responded to again.
The request is to be able to have `minibuffer-message'
output logged, WITHOUT calling `message'.
You seem to keep repeating that we can have the effect
of logging the text (and have the UI effect of only
`minibuffer-message') by ALSO calling `message'.
That's not the request. It's not about whether one
can get the effect of logging `minibuffer-message'
output without also logging a `message' output for
the same text.
It's about simply controlling logging for
`minibuffer-message', totally, completely, independent
of any use of `message'.
IOW, please forget about `message'. The request is
for a simple way to (optionally) log output of
`minibuffer-message', just as we do, for example for
`message' output. And without recourse to any call
to `message' - no workaround, just a simple way to
log `minibuffer-message'. We have such a way for
`message' output. The request is for such a way for
`minibuffer-message' output - totally independent
from `message'.
> > Eli seems to have clearly misunderstood the request.
>
> Please don't second-guess my misunderstandings. It is rude, to say
> the least.
Fair enough to say that I do think you've misundertood?
Perhaps you prefer RMS's favorite way to put it: "We
seem to be miscommunicating."
You reply that what I say is obvious to all and doesn't
need to be said. I reply that I think you're not
getting what I'm saying. You reply that there's a
workaround (which I could say is obvious to all and
doesn't need to be reiterated).
I reply that I'm aware of that workaround, and I'm
asking for a _simple_ way to do what's requested,
along the lines of what's available for `message',
for instance.
> > 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.
Not simply. Not in a way similar or analogous to
what we can do for `message'. Not without jumping
through a hoop - also calling `message'.
Please keep `message' out of it. This request is
about `minibuffer-message'.
next parent reply other threads:[~2020-08-22 18:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2020-08-22 18:34 ` bug#3465: 23.0.94; feature request: be able to log minibuffer messages Lars Ingebrigtsen
2020-08-22 18:36 ` bug#4477: " Eli Zaretskii
2009-06-03 21:38 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 ` 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=028c363a-e801-4c9a-8ebd-d55180961cf7@default \
--to=drew.adams@oracle.com \
--cc=3465@debbugs.gnu.org \
--cc=4477@debbugs.gnu.org \
--cc=bojohan@gnu.org \
--cc=eliz@gnu.org \
--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.