From: Richard Stallman <rms@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: lgorrie@common-lisp.net, sheepduke@gmail.com,
emacs-devel@gnu.org, luke@snabb.co, myself@spensertruex.com,
joaotavora@gmail.com, heller@common-lisp.net,
monnier@iro.umontreal.ca
Subject: Re: Common Lisp in Emacs (lisp-mode, font-lock, SLIME, SLY, ...)
Date: Tue, 14 Apr 2020 22:55:35 -0400 [thread overview]
Message-ID: <E1jOYD9-0004ly-3R@fencepost.gnu.org> (raw)
In-Reply-To: <xjfa73ewf73.fsf@sdf.org> (message from Andrea Corallo on Tue, 14 Apr 2020 10:10:24 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I think you could be missing the humour within the SLIME name. This
> stands for "Superior Lisp Interaction Mode for Emacs".
I didn't know that -- thanks for informing me.
I have a hunch I am far from the only person who sees the name SLIME
and does not know what it stands for. I saw several messages about it
on this list, and I don't think any of them explained, until you did
just now.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-04-15 2:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 22:59 Common Lisp in Emacs (lisp-mode, font-lock, SLIME, SLY, ...) Stefan Monnier
2020-04-11 4:58 ` Luke Gorrie
2020-04-12 2:41 ` Richard Stallman
2020-04-12 6:05 ` Luke Gorrie
2020-04-13 2:21 ` Richard Stallman
2020-04-13 18:14 ` Luke Gorrie
2020-04-14 2:18 ` Richard Stallman
2020-04-14 2:24 ` 조성빈 via "Emacs development discussions.
2020-04-15 2:58 ` Richard Stallman
2020-04-14 10:10 ` Andrea Corallo
2020-04-15 2:55 ` Richard Stallman [this message]
2020-04-12 4:45 ` Stefan Monnier
2020-04-11 5:36 ` Teemu Likonen
2020-04-11 15:38 ` João Távora
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1jOYD9-0004ly-3R@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=heller@common-lisp.net \
--cc=joaotavora@gmail.com \
--cc=lgorrie@common-lisp.net \
--cc=luke@snabb.co \
--cc=monnier@iro.umontreal.ca \
--cc=myself@spensertruex.com \
--cc=sheepduke@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).