From: "João Távora" <joaotavora@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Kangas <stefan@marxist.se>,
Stefan Monnier <monnier@iro.umontreal.ca>,
"49278@debbugs.gnu.org" <49278@debbugs.gnu.org>
Subject: bug#49278: [External] : bug#49278: 28.0.50; Lisp Mode is for Common Lisp
Date: Tue, 28 Sep 2021 00:36:37 +0100 [thread overview]
Message-ID: <CALDnm51c2Ng2uYwuaAdcsU1bWiF8otsXVE0jVQ0A7NLa+wSc9Q@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488F39277DEDB206C7C4ABCF3A79@SJ0PR10MB5488.namprd10.prod.outlook.com>
On Tue, Sep 28, 2021 at 12:25 AM Drew Adams <drew.adams@oracle.com> wrote:
> It matters, I think, if the mode is called "Lisp mode".
Yes, it's true. The name is unfortunate. There are many Lisps,
but "Lisp mode" is designed to work with only one of them, Common
Lisp.
Renaming the mode to clarify an option IMO. Maybe, if it has no impacts.
_Then_ would you agree to "Common Lisp mode is for Common Lisp"?
Everybody that codes Common Lisp knows it by 'lisp-mode' and there
are many tools that use that name. Maybe we could make an alias?
Anyway, just _because_ it happens to be called Lisp Mode, erroneously,
doesn't make it suitable for more Lisps magically. If I start calling you
Michael Jordan, and the name somehow sticks, I doubt you'll ever become
a professional basketball player as a result. Many people will make that
assumption and you'll have to clearly state that you're not (you're not,
right?) in your user's manual.
João
next prev parent reply other threads:[~2021-09-27 23:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 18:06 bug#49278: 28.0.50; Lisp Mode is for Common Lisp João Távora
2021-06-29 18:16 ` Eli Zaretskii
2021-06-29 18:25 ` João Távora
2021-06-30 12:35 ` Eli Zaretskii
2021-06-30 12:45 ` João Távora
2021-06-29 20:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-29 20:55 ` João Távora
2021-06-29 22:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-30 12:47 ` Eli Zaretskii
2021-06-30 12:37 ` Eli Zaretskii
2021-06-30 13:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-30 13:21 ` João Távora
2021-06-30 13:29 ` Eli Zaretskii
2021-06-30 13:32 ` João Távora
2021-06-30 13:51 ` Eli Zaretskii
2021-06-30 14:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-30 14:50 ` João Távora
2021-06-30 15:54 ` Eli Zaretskii
2021-06-30 16:02 ` João Távora
2021-06-30 15:52 ` Eli Zaretskii
2021-06-30 16:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-30 16:47 ` Eli Zaretskii
2021-06-30 16:50 ` João Távora
2021-06-30 16:55 ` Eli Zaretskii
2021-06-30 16:58 ` João Távora
2021-06-30 14:54 ` João Távora
2021-06-30 15:55 ` Eli Zaretskii
2021-06-30 15:58 ` João Távora
2021-06-30 16:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-30 3:50 ` Phil Hagelberg
2021-06-30 9:44 ` João Távora
2021-09-24 23:01 ` Stefan Kangas
2021-09-24 23:23 ` João Távora
2021-09-25 0:22 ` Stefan Kangas
2021-09-25 1:26 ` bug#49278: [External] : " Drew Adams
2021-09-25 1:35 ` Lars Ingebrigtsen
2021-09-25 6:42 ` Eli Zaretskii
2021-09-25 1:13 ` bug#49278: [External] : " Drew Adams
2021-09-25 9:02 ` João Távora
2021-09-25 16:03 ` Drew Adams
2021-09-25 16:43 ` Stefan Kangas
2021-09-25 17:24 ` Drew Adams
2021-09-27 20:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-27 22:05 ` Drew Adams
2021-09-27 22:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-27 23:24 ` Drew Adams
2021-09-27 23:36 ` João Távora [this message]
2021-09-28 2:17 ` Drew Adams
2021-09-28 2:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-28 2:31 ` Drew Adams
2021-09-28 2:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-27 14:48 ` Jean Louis
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=CALDnm51c2Ng2uYwuaAdcsU1bWiF8otsXVE0jVQ0A7NLa+wSc9Q@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=49278@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.