From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: how to turn this Gnus function into a macro?
Date: Thu, 08 Jan 2004 15:30:13 -0500 [thread overview]
Message-ID: <4n4qv6ji96.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <b9yr7yb0yat.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 08 Jan 2004 15:06:18 +0900")
I think I'll keep the function form since it's significantly faster
than the macro, but seeing yours and Jeremy's solutions taught me lots
about macros - thanks! That will help me understand a lot of the Gnus
and Emacs internals.
Ted
prev parent reply other threads:[~2004-01-08 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 22:19 Ted Zlatanov
2004-01-07 22:55 ` Jesper Harder
2004-01-08 0:09 ` Ted Zlatanov
2004-01-08 4:13 ` Jesper Harder
2004-01-08 2:13 ` Katsumi Yamaoka
2004-01-08 3:28 ` Ted Zlatanov
2004-01-08 3:33 ` Katsumi Yamaoka
2004-01-08 3:42 ` Jeremy Maitin-Shepard
2004-01-08 3:47 ` Katsumi Yamaoka
2004-01-08 4:06 ` Jeremy Maitin-Shepard
2004-01-08 6:06 ` Katsumi Yamaoka
2004-01-08 20:30 ` Ted Zlatanov [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=4n4qv6ji96.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--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).