Re: Redirecting messages (was: Proposed new core library: alert.el)

[Daniel Colascione <dancol@dancol.org>]

[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]

On 11/06/2015 01:23 AM, Artur Malabarba wrote:
> On 5 Nov 2015 7:48 pm, "Ted Zlatanov" <tzz@lifelogs.com> wrote:
>>
>> Agreed.  But if alert.el doesn't support it now, it should have a way to
>> replace `message' so rather than asking every package to change, the
>> user just customizes one thing globally.
> 
> I don't think users will want to turn every single message into a
> desktop notification. The `message' function has always been a very
> non-intrusive approach, so it's used in very spammy ways sometimes.
> 
> That said, a way of redirecting messages via some arbitrary function
> is something that would be nice to have, and it's been mentioned
> lately here. I think Stefan was pushing for this a bit, specially when
> Oleh implemented the new inhibit-messages variable.
> 
> The right approach IMO is to
> 
> 1. move the current message function to `message-echo-area'
> 2. define a variable called `message-function', whose default value is
> #'message-echo-area
> 3. redefine the `message' function to just call the value of
> `message-function' and then log the string to the  *Messages* buffer

I wish we'd direct some love toward the streams system. There's no
reason that standard-output and a hypothetical message-output couldn't
be the same type of object and have the same semantics. A scheme like
this would also help modes like ielm provide a uniform way of capturing
command output.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]