From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: nljlistbox2@gmail.com, 27170@debbugs.gnu.org, rms@gnu.org,
stefankangas@gmail.com
Subject: bug#27170: 26.0.50; Suggestion: Optionally send package build output to log file not *Messages*
Date: Sun, 30 Jan 2022 18:48:56 +0200 [thread overview]
Message-ID: <83leyx9nk7.fsf@gnu.org> (raw)
In-Reply-To: <87sft5b4pz.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 30 Jan 2022 16:52:56 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: rms@gnu.org, nljlistbox2@gmail.com, 27170@debbugs.gnu.org,
> stefankangas@gmail.com
> Date: Sun, 30 Jan 2022 16:52:56 +0100
>
> > So basically, binding this variable will actually _split_ the messages
> > between *Messages* and some other buffer.
>
> Of course a binding has no effect on code that runs after the binding is
> over -- we don't note this in the documentation for, say,
> `print-length', so I'm not sure why we'd note this in relation to this
> variable either.
The point I was trying to make was that echo-area messages we see
don't necessarily come from code of the command, and so having a
command bind the variable might not catch all of the messages.
next prev parent reply other threads:[~2022-01-30 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 16:51 bug#27170: 26.0.50; Suggestion: Optionally send package build output to log file not *Messages* N. Jackson
2020-08-20 16:08 ` Lars Ingebrigtsen
2020-08-20 16:34 ` Philipp Stephani
2020-08-20 16:43 ` Lars Ingebrigtsen
2020-08-20 17:38 ` Stefan Kangas
2020-08-21 11:09 ` Lars Ingebrigtsen
2020-08-22 3:51 ` Richard Stallman
2022-01-29 16:24 ` Lars Ingebrigtsen
2022-01-29 17:30 ` Eli Zaretskii
2022-01-30 15:52 ` Lars Ingebrigtsen
2022-01-30 16:48 ` Eli Zaretskii [this message]
2020-08-22 11:29 ` Stefan Kangas
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=83leyx9nk7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27170@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=nljlistbox2@gmail.com \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.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 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.