From: Juanma Barranquero <lekktu@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: delayed-warnings-hook versus deferred-action-function
Date: Wed, 8 Feb 2012 05:28:35 +0100 [thread overview]
Message-ID: <CAAeL0STDgqNkKL6qWhT7jjPvXOnRMEW29BFhfwutyyfQUpAZkw@mail.gmail.com> (raw)
In-Reply-To: <sgzkcu0y9i.fsf@fencepost.gnu.org>
> Trying to document this, I'm confused as to what this functionality is
> for. It only seems to be used for warning about a _emacs file on MS
> Windows?
And also for the case that HOME is being defaulted to C:\ (because
there's a .emacs in C:\) but not set explicitly. That was, in fact,
the original use, because at that point elisp code can not yet run.
> Is it supposed to be used by external Lisp libraries for
> something (if so, what?), or is it fully internal to Emacs (in which it
> may not need documenting anywhere)?
I'd say it is more for internal use. I'd like to see some warnings
that currently are generated through l?warn and display-warning turned
into delayed warnings, for two reasons: eventually it will allow the
user to filter them out or otherwise customize them, and it allows
more control in some cases. For example, in bug#10578 I proposed it as
a way to display errors from the redisplay and image library code in a
relatively unobtrusive way (using an idle timer).
Anway, if we supply a trivial macro
(defmacro delay-warning (&rest args)
"...
\n(fn type message &optional level buffer-name)"
`(push args delayed-warnings-list))
there's no reason it could not be used from external libraries.
Juanma
next prev parent reply other threads:[~2012-02-08 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 0:06 delayed-warnings-hook versus deferred-action-function Glenn Morris
2012-02-05 0:29 ` Juanma Barranquero
2012-02-05 2:25 ` Glenn Morris
2012-02-08 4:01 ` Glenn Morris
2012-02-08 4:28 ` Juanma Barranquero [this message]
2012-02-08 8:32 ` Glenn Morris
2012-02-08 10:02 ` Juanma Barranquero
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=CAAeL0STDgqNkKL6qWhT7jjPvXOnRMEW29BFhfwutyyfQUpAZkw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.