Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: bbdb-info@lists.sourceforge.net
Cc: ding@gnus.org
Subject: Re: gnus-article-prepare-hook and friends
Date: Fri, 18 Feb 2011 15:18:45 -0800	[thread overview]
Message-ID: <877hcx0w4q.fsf@gnus.org> (raw)
In-Reply-To: <87aahx7cuw.fsf@gmail.com>

Antoine Levitt <antoine.levitt@gmail.com> writes:

> The following certainly does the trick, and looks like a more reasonable
> place for gnus-article-prepare-hook (docstring says "after an article
> has been prepared in the article buffer.") However, I'm not sure whether
> or not it breaks other code that depends on its behaviour.

Thanks; applied.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


      reply	other threads:[~2011-02-18 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 17:03 Antoine Levitt
2011-02-14 20:15 ` Lars Ingebrigtsen
2011-02-15 11:31   ` Antoine Levitt
2011-02-18 23:18     ` Lars Ingebrigtsen [this message]

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=877hcx0w4q.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=bbdb-info@lists.sourceforge.net \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).