From: Luke Gorrie <luke@snabb.co>
To: rms@gnu.org
Cc: Luke Gorrie <lgorrie@common-lisp.net>,
sheepduke@gmail.com, emacs-devel@gnu.org,
myself@spensertruex.com, heller@common-lisp.net,
joaotavora@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Common Lisp in Emacs (lisp-mode, font-lock, SLIME, SLY, ...)
Date: Sun, 12 Apr 2020 08:05:34 +0200 [thread overview]
Message-ID: <CAA2XHbdTq3B8SoDJ-nAtJVG866o+uxMHgmHYHXBFGHG-WfMXCw@mail.gmail.com> (raw)
In-Reply-To: <E1jNSYz-000328-PU@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Sun, 12 Apr 2020, 04:41 Richard Stallman, <rms@gnu.org> wrote:
> [[[ 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. ]]]
>
> Why call it "SLIME"?
>
Eric Marsden wrote it originally as a quick weekend hack and named the
files slim.el and skank.lisp after the song he was listening to at the time
(Fat Boy Slim.)
I picked up development and renamed the files slime.el and swank.lisp so
the buffer names wouldn't collide in my Emacs session.
Hadn't anticipated that the code would be so long lived or maybe we could
have chosen a better name :).
>
[-- Attachment #2: Type: text/html, Size: 1328 bytes --]
next prev parent reply other threads:[~2020-04-12 6:05 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA2XHbdTq3B8SoDJ-nAtJVG866o+uxMHgmHYHXBFGHG-WfMXCw@mail.gmail.com \
--to=luke@snabb.co \
--cc=emacs-devel@gnu.org \
--cc=heller@common-lisp.net \
--cc=joaotavora@gmail.com \
--cc=lgorrie@common-lisp.net \
--cc=monnier@iro.umontreal.ca \
--cc=myself@spensertruex.com \
--cc=rms@gnu.org \
--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 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.