unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: delayed-warnings-list and delayed-warnings-hook
Date: Mon, 02 Apr 2012 21:58:25 +0800	[thread overview]
Message-ID: <87iphip75q.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STgjeY_sG20AYxPJatRdWJV5_hUuPR+DKRsGZJyhcJCUw@mail.gmail.com> (Juanma Barranquero's message of "Tue, 20 Mar 2012 11:07:20 +0100")

Juanma Barranquero <lekktu@gmail.com> writes:

>> Is there any reason the NEWS entry for this is tagged `---'?  As far as
>> I can tell, it is an ordinary new feature and should be documented.
>
> Glenn added the --- and the following comment in the code:
>
> +;; At present this is only really useful for Emacs internals.
> +;; Document in the lispref if it becomes generally useful.
> +;; Ref http://lists.gnu.org/archive/html/emacs-devel/2012-02/msg00085.html
>
> It is only used for Emacs internals, but I think it is useful in general.

`delayed-warnings-list' should certainly be documented; I will work on
that.

As for `delayed-warnings-hook', maybe we should mark it explicitly as
internal, because it seems a bit delicate with respect to third party
usage.  Because of the default value (collapse-delayed-warnings
display-delayed-warnings), in order not to deal with uncollapsed
messages, third party code needs to append to the hook, and must not
prepend to it.  But this makes it difficult for one third party package
to give its function priority over other third party packages.  This
design kind of bothers me.

To clarify the situation a little, could you explain what kind of
functions you envision third party code adding to this hook?



  reply	other threads:[~2012-04-02 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  9:56 delayed-warnings-list and delayed-warnings-hook Chong Yidong
2012-03-20 10:07 ` Juanma Barranquero
2012-04-02 13:58   ` Chong Yidong [this message]
2012-04-02 14:20     ` Juanma Barranquero
2012-04-02 14:22       ` Juanma Barranquero
2012-03-20 16:24 ` Glenn Morris

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=87iphip75q.fsf@gnu.org \
    --to=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@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).