all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-devel@gnu.org
Subject: Re: Redirecting messages
Date: Fri, 06 Nov 2015 10:38:59 +0100	[thread overview]
Message-ID: <87lhab1n7w.fsf@gmx.us> (raw)
In-Reply-To: CAAdUY-LP6FvcVV6hQQR1WTg1m9kx5rO6Z=KZGYQteM2EoiAKyw@mail.gmail.com

Artur Malabarba <bruce.connor.am@gmail.com> writes:

> 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.

Indeed, this would be nice.  I would like to be able to be notified when a
time-consuming R script has completed or when Org is done compiling my
PDF; tramp is done copying many files, etc.

Perhaps it would be nice if the default would already check some custom
variable consisting of cons of

      (FUN or regexp for evaluating message . FUN or String to notify)

Or each user can add this in her own custom message function.

Rasmus

-- 
ツ




  parent reply	other threads:[~2015-11-06  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  9:23 Redirecting messages (was: Proposed new core library: alert.el) Artur Malabarba
2015-11-06  9:31 ` Daniel Colascione
2015-11-06 21:54   ` File-handle streams (was: Redirecting messages) John Wiegley
2015-11-06  9:38 ` Rasmus [this message]
2015-11-06 20:48   ` Redirecting messages John Wiegley
2015-11-06 15:57 ` John Wiegley
2015-11-07  1:23   ` raman
2015-11-06 21:55 ` John Wiegley

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=87lhab1n7w.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-devel@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 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.