unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: "N. Jackson" <nljlistbox2@gmail.com>, 27170@debbugs.gnu.org
Subject: bug#27170: 26.0.50; Suggestion: Optionally send package build output to log file not *Messages*
Date: Thu, 20 Aug 2020 18:43:12 +0200	[thread overview]
Message-ID: <87sgchp8tb.fsf@gnus.org> (raw)
In-Reply-To: <CAArVCkSj4amqPQQ3btbqdchsf_rLWOTrKU8nOzQS27qmaKVgvg@mail.gmail.com> (Philipp Stephani's message of "Thu, 20 Aug 2020 18:34:28 +0200")

Philipp Stephani <p.stephani2@gmail.com> writes:

> I don't think we can rename the *Messages* buffer. We document that
> its name is *Messages*, and there's certainly tons of code around that
> assumes that.

I'm not talking about renaming the *Messages* buffer -- just being able
to redirect messages to a different buffer if we want to.

> If we want to change anything in this area, we'd better DTRT and
> introduce a proper logging framework, with customizable log sources
> and sinks (the *Messages* buffer being one of the sinks).

Sounds like overkill to me.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-08-20 16:43 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 [this message]
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
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

  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=87sgchp8tb.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=27170@debbugs.gnu.org \
    --cc=nljlistbox2@gmail.com \
    --cc=p.stephani2@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 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).