Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: bugs@gnus.org, ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: gnus-util.el loads rmail
Date: Fri, 05 Dec 2003 11:52:28 +0900	[thread overview]
Message-ID: <b9yn0a82cyb.fsf@jpl.org> (raw)
In-Reply-To: <microsoft-free.87wu9cawe9.fsf@eicq.dnsalias.org>

>>>>> In <microsoft-free.87wu9cawe9.fsf@eicq.dnsalias.org>
>>>>>	Steve Youngs <sryoungs@bigpond.net.au> wrote:

KY> Loading of rmail is only for the `rmail-select-summary' macro,
KY> isn't it?  If so, it can be solved by not compiling that section:

[...]

KY> How about it?

> So this would be as a replacement to Jerry's patch or in addition to
> it?

No, that's only for explaining my idea.  Maybe, it should be
performed to gnus-util.el before you change.  If you allow, I
need to do work.

> And the doc string from `dont-compile' troubles me a little...

[...]

>| If you think you need this, you're probably making a mistake somewhere.

> ...that last line in particular.

About the case where `eval' is used in the Lisp source, there
was a similar description in very old Info documents.
`dont-compile' is an another expression of `eval' and `quote':

(macroexpand '(dont-compile FORM))
 => (eval (quote FORM))

It is used in order to express the purpose more clearly.
Besides making the operation slow a bit, there is no problem.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



  reply	other threads:[~2003-12-05  2:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  0:45 Katsumi Yamaoka
2003-12-05  1:25 ` Steve Youngs
2003-12-05  2:52   ` Katsumi Yamaoka [this message]
2003-12-07 20:25     ` Steve Youngs
2003-12-08  2:35       ` Katsumi Yamaoka
2003-12-08  4:15         ` Steve Youngs
2003-12-08  9:01           ` Katsumi Yamaoka
2003-12-08 20:05             ` Steve Youngs

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=b9yn0a82cyb.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=xemacs-beta@xemacs.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).