From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Agent Customization check-in
Date: Sun, 02 Mar 2003 20:42:57 -0600 [thread overview]
Message-ID: <u65r1uq4u.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <yotl65r1rzer.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Hi,
>
>>>>>> In <uvfz1i7gv.fsf@xpediantsolutions.com>
>>>>>> Kevin Greiner <kgreiner@xpediantsolutions.com> wrote:
>
>> Just to let everyone know, I just finished a rather large check-in.
>
> As you know, RMS requires that cl run-time functions should not
> be used. However, in the functions gnus-category-edit-predicate,
> gnus-category-edit-score and gnus-category-edit-groups, you used
> the setf macro which is provided by cl-macs.el in the backquoted
> forms. They all require cl at the run-time.
>
> We should take care not to use cl in everyday life.
>
Thanks.
The setf forms have been removed.
Kevin
prev parent reply other threads:[~2003-03-03 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 1:06 Kevin Greiner
2003-03-03 1:50 ` Katsumi Yamaoka
2003-03-03 2:42 ` Kevin Greiner [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=u65r1uq4u.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).