From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: message-yank-original issue
Date: Mon, 14 Mar 2011 20:36:32 -0400 [thread overview]
Message-ID: <87k4g1nrsf.fsf@maru.md5i.com> (raw)
In-Reply-To: <87d3lte7qs.fsf@gmail.com> (Antoine Levitt's message of "Mon, 14 Mar 2011 22:02:03 +0100")
Antoine Levitt <antoine.levitt@gmail.com> writes:
> 14/03/11 20:47, Ted Zlatanov:
>
>> For non-Gnus code (and message.el recently became a standalone part of
>> Emacs, loaded without Gnus) it's better to be prudent and stay away from
>> CL functions and macros.
>
> But what's the rationale behind not loading it as part of the standard
> emacs load? Is it a loading time issue? The command
>
> time emacs -nw -Q --eval "(require 'cl)" --eval "(kill-emacs)"
>
> does not appear to be noticeably longer than the same one without cl, on
> the two machines I've tried. (but maybe they're both too fast to measure
> it)
My understanding is that the reason is twofold:
1) The cl functions don't have their own namespace.
2) The cl functions don't follow the same conventions as emacs lisp.
(Keyword arguments being a good example.
These are what I recall RMS's objections to be, and are not mine. (I
require cl as the very first non-comment in my .emacs.el.)
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2011-03-15 0:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 10:11 Gnus bugfixing is broken David Kastrup
2011-03-14 14:47 ` Lars Magne Ingebrigtsen
2011-03-14 15:17 ` David Kastrup
2011-03-14 16:12 ` Adam Sjøgren
2011-03-14 17:47 ` Sivaram Neelakantan
2011-03-14 16:22 ` Lars Magne Ingebrigtsen
2011-03-14 19:13 ` message-yank-original issue (was: Gnus bugfixing is broken.) Ted Zlatanov
2011-03-14 19:38 ` message-yank-original issue Antoine Levitt
2011-03-14 19:47 ` Ted Zlatanov
2011-03-14 21:02 ` Antoine Levitt
2011-03-14 22:04 ` Ted Zlatanov
2011-03-15 0:36 ` Michael Welsh Duggan [this message]
2011-03-15 15:30 ` Lars Magne Ingebrigtsen
2011-03-15 15:29 ` Lars Magne Ingebrigtsen
2011-03-15 15:49 ` Ted Zlatanov
2011-03-15 15:56 ` Lars Magne Ingebrigtsen
2011-03-15 9:34 ` Ted Zlatanov
2011-03-15 9:48 ` David Kastrup
2011-03-15 10:01 ` Ted Zlatanov
2011-03-26 19:34 ` Sven Joachim
2011-03-28 19:05 ` Ted Zlatanov
2011-03-28 19:57 ` Sven Joachim
2011-03-28 20:06 ` Ted Zlatanov
2011-03-28 20:35 ` Stefan Monnier
2011-03-29 5:37 ` Antoine Levitt
2011-03-28 20:41 ` Stefan Monnier
2011-03-29 14:55 ` Ted Zlatanov
2011-03-29 15:08 ` David Kastrup
2011-03-29 15:20 ` Gnus compatibility with the lexical binding branch (was: message-yank-original issue) Ted Zlatanov
2011-03-29 20:16 ` Gnus compatibility with the lexical binding branch Stefan Monnier
2011-03-29 20:53 ` Ted Zlatanov
2011-03-30 0:42 ` Stefan Monnier
2011-04-08 5:51 ` Ted Zlatanov
2011-03-15 10:06 ` Gnus bugfixing is broken Ted Zlatanov
2011-03-15 13:31 ` Didier Verna
2011-03-15 13:52 ` Ted Zlatanov
2011-03-15 15:23 ` Lars Magne Ingebrigtsen
2011-03-15 15:56 ` Ted Zlatanov
2011-03-15 16:09 ` Lars Magne Ingebrigtsen
2011-03-15 17:01 ` Didier Verna
2011-03-15 13:58 ` Michael Albinus
2011-03-15 14:46 ` Didier Verna
2011-03-15 14:57 ` Ted Zlatanov
2011-03-15 15:08 ` Michael Albinus
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=87k4g1nrsf.fsf@maru.md5i.com \
--to=md5i@md5i.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).