From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: martin rudalics <rudalics@gmx.at>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Delayed warnings
Date: Tue, 22 Mar 2011 12:59:02 +0100 [thread overview]
Message-ID: <AANLkTimZQg7Ux4G7rt26cAHzZCEcnnHsdQuc8nsh2MmS@mail.gmail.com> (raw)
In-Reply-To: <jwvipvcgmi5.fsf-monnier+emacs@gnu.org>
On Mon, Mar 21, 2011 at 23:05, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> Or you could have your C code all `add-hook-once' on post-command-hook
> which would be a new function that adds a function onto a hook such that
> the function is only run once and then automatically removed.
I like Martin's proposal more, for two reasons (in addition to the
concern expressed by him about errors in post-command-hook):
1.- I want to allow the user to easily disable these warnings from
their .emacs; it's cleaner to locate '(initialization "such and such
warning" :warning) in the delayed-warnings variable than a lambda
expression.
2.- What you propose is more general, but it adds complexity for the
simple case of just wanting to display a warning, and that generality
is not really needed IMO, unless you envision there's a common need to
delay things other than errors and warnings and the like. I'd say the
limited success of `deferred-action-*' would seem to indicate there
isn't any such need, and for those rare cases, they have
post-command-hook.
So, summarizing: I have nothing again `add-hook-once' and surely will
find it useful (my .emacs would benefit from it right now); but I
don't think it's the right thing to use for delayed initialization
warnings.
Juanma
next prev parent reply other threads:[~2011-03-22 11:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 5:44 Delayed warnings Juanma Barranquero
2011-03-21 8:01 ` martin rudalics
2011-03-21 12:01 ` Juanma Barranquero
2011-03-21 13:17 ` martin rudalics
2011-03-21 13:43 ` Eli Zaretskii
2011-03-21 18:06 ` martin rudalics
2011-03-21 14:48 ` Juanma Barranquero
2011-03-21 18:06 ` martin rudalics
2011-03-21 20:19 ` Juanma Barranquero
2011-03-21 22:05 ` Stefan Monnier
2011-03-22 7:59 ` martin rudalics
2011-03-22 11:59 ` Juanma Barranquero [this message]
2011-03-23 13:50 ` Jeff Sparkes
2011-03-25 13:10 ` Juanma Barranquero
2011-04-27 0:55 ` Juanma Barranquero
2011-04-27 3:05 ` Eli Zaretskii
2011-04-27 11:27 ` Juanma Barranquero
2011-04-27 17:32 ` Stefan Monnier
2011-04-27 22:11 ` Juanma Barranquero
2011-04-28 0:40 ` Stefan Monnier
2011-04-28 0:59 ` Juanma Barranquero
2011-04-28 15:26 ` Stefan Monnier
2011-04-28 16:22 ` Juanma Barranquero
2011-04-28 18:39 ` Stefan Monnier
2011-05-08 17:58 ` Chong Yidong
2011-05-08 18:43 ` Juanma Barranquero
2011-05-09 14:15 ` Stefan Monnier
2011-05-09 18:28 ` Richard Stallman
2011-03-22 7:58 ` martin rudalics
2011-03-22 12:04 ` 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
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=AANLkTimZQg7Ux4G7rt26cAHzZCEcnnHsdQuc8nsh2MmS@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).