bug#27170: 26.0.50; Suggestion: Optionally send package build output to log file not *Messages*

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

> The "bind" part (also in the doc string of the variable) might mislead
> someone into thinking that just binding this variable around some form
> is enough to have all the relevant messages to go to that buffer.

I think most people know that that's what binding means...?

> But that is not necessarily true, because some messages are produced
> after the command exits; a prominent example is messages produced by
> the display engine.
>
> 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.

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