From: Matt Armstrong <matt@rfc20.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59317@debbugs.gnu.org
Subject: bug#59317: 29.0.50; Feature idea: suppress `message' output in ert batch test output
Date: Wed, 16 Nov 2022 21:51:46 -0800 [thread overview]
Message-ID: <87mt8qruvh.fsf@rfc20.org> (raw)
In-Reply-To: <834juyfzfi.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Matt Armstrong <matt@rfc20.org>
>> Date: Wed, 16 Nov 2022 10:52:11 -0800
>>
>> A good number of Emacs tests exercise parts of Emacs that call
>> `message'.
>
> Are you sure? Many Emacs features display text that doesn't go
> through 'message'.
>
>> Idea: hide `message' output when running in batch mode, printing them
>> only for failed tests.
>
> We have set-message-function that could be used for this purpose, I
> think? If indeed 'message' is the culprit.
It looks like the set-message-function(s) hooks are bypassed in
non-interactive mode. In that case message3_nolog in xdisp.c calls
message_to_stderr, instead of calling set_message. It is set_message
that ultimately uses the set-message-function machinery.
After looking at this more I agree with your suspicions. It looks like
good amount of C level code calls various message functions without
going through Fmessage. Also, I spot no easy way to modify ert.el to
temporarily redirect stderr elsewhere. In noninteractive mode Emacs
seems hard coded to print to stderr.
I proposed this thinking it would be an easy and simple change. At this
point I'm thinking the effort and complexity here isn't worth it. If
nobody else wants to champion this idea I'll go ahead and close it.
next prev parent reply other threads:[~2022-11-17 5:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 18:52 bug#59317: 29.0.50; Feature idea: suppress `message' output in ert batch test output Matt Armstrong
2022-11-16 19:54 ` Eli Zaretskii
2022-11-17 0:12 ` Stefan Kangas
2022-11-17 6:06 ` Matt Armstrong
2022-11-17 6:39 ` Eli Zaretskii
2022-11-17 7:28 ` Stefan Kangas
2022-11-17 5:51 ` Matt Armstrong [this message]
2022-11-17 7:13 ` Eli Zaretskii
2022-11-17 10:36 ` Michael Albinus
2022-11-17 10:49 ` Stefan Kangas
2022-11-17 12:35 ` Michael Albinus
2022-11-18 0:12 ` Matt Armstrong
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=87mt8qruvh.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=59317@debbugs.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 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).