all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: emacs-devel@gnu.org
Subject: Re: is requiring cl bad?
Date: Sun, 16 Dec 2012 11:26:10 +0100	[thread overview]
Message-ID: <8738z6gunx.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 20121216181444.f9963d105a193f14f78e6f83@gmail.com

Xue Fuqiao <xfq.free@gmail.com> writes:

> On Sun, 16 Dec 2012 10:29:30 +0100
> Ivan Kanis <ivan.kanis@googlemail.com> wrote:
>
>> I was under the impression that requiring cl was bad (TM). I can't
>> remember why. Is it still so?
>
> You can see these pages:
> http://lists.gnu.org/archive/html/emacs-devel/2003-08/msg00436.html
> http://www.gnu.org/gnu/rms-lisp.html
> http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg01472.html
>
> BTW, what does "TM" mean(English is not my native language)?

It should be written as: ™  meaning Trade Mark, meaning "cl is bad" is a
registered trade mark.  No it's not, but it's as famous as if it was.

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.




  reply	other threads:[~2012-12-16 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16  9:29 is requiring cl bad? Ivan Kanis
2012-12-16 10:14 ` Xue Fuqiao
2012-12-16 10:26   ` Pascal J. Bourguignon [this message]
2012-12-16 10:36     ` Xue Fuqiao
2012-12-16 11:00   ` Ivan Kanis
2012-12-16 17:06 ` Stefan Monnier
2012-12-17 19:09   ` Pascal J. Bourguignon
2012-12-18  1:58     ` Tony Day
2012-12-20  4:46     ` David De La Harpe Golden
2012-12-20  5:20       ` Ivan Kanis
2012-12-20  9:16       ` Helmut Eller
2012-12-21  7:05         ` David De La Harpe Golden
2012-12-21  9:24           ` Helmut Eller
2012-12-17 20:58   ` Ivan Kanis
2012-12-18  4:04     ` Stefan Monnier

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=8738z6gunx.fsf@kuiper.lan.informatimago.com \
    --to=pjb@informatimago.com \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.