From: "João Távora" <joaotavora@gmail.com>
To: 49278@debbugs.gnu.org
Cc: monnier@iro.umontreal.ca
Subject: bug#49278: 28.0.50; Lisp Mode is for Common Lisp
Date: Tue, 29 Jun 2021 19:06:19 +0100 [thread overview]
Message-ID: <87y2asa6lg.fsf@gmail.com> (raw)
Hi,
It's been the status quo for a long time now that Lisp Mode is the Emacs
major mode for editing Common Lisp programs. The SLIME and SLY packages
are popular amongst CL programmers and have relied on this fact for many
years (SLIME in I think has been the tool of choice for Emacs+CL for
more than 15 years).
In addition, there are many references to "Common Lisp" in lisp-mode.el.
In addition, non-CL-lisps have also historically used their own major
modes derived from prog-mode. Examples are Emacs lisp mode, Scheme mode
and Clojure mode.
In addition, there is in Emacs 27.1 a new lisp-data-mode. That is
useful for defining using define-derived-mode to make Lisp-like major
modes derived from commonly found Lisp-style functionality such as
parenthesis-matching syntax tables and such.
However, the docstring of lisp-mode, the function, still states that it
is used for "Lisps other than GNU Emacs Lisp". Likely this docstring
was written when Common Lisp was still young and intended to group its
closely-related Lisp brethren (MacLisp, Franz Lisp, etc) in mind.
Those variants are now gone, we should update lisp-mode.el's docstring
to reflect the state of things, since a fraction of people seem to be
misusing lisp-mode to derive new major modes for new niche Lisps, where
they should be using lisp-data-mode (perhaps they are not aware of it).
See also:
https://gitlab.com/technomancy/fennel-mode/-/issues/11
https://github.com/joaotavora/sly/issues/339
https://emacs.stackexchange.com/questions/18646/why-isnt-emacs-lisp-mode-derived-from-lisp-mode/18652#18652
João
To fix this, I suggest this documentation patch.
diff --git a/doc/emacs/building.texi b/doc/emacs/building.texi
index 8de93867ba..7d655449c5 100644
--- a/doc/emacs/building.texi
+++ b/doc/emacs/building.texi
@@ -1764,10 +1764,10 @@ External Lisp
@cindex mode, Lisp
@cindex Common Lisp
- Lisp mode is the major mode for editing programs written in
-general-purpose Lisp dialects, such as Common Lisp. Its mode command
-is @kbd{M-x lisp-mode}. Emacs uses Lisp mode automatically for files
-whose names end in @file{.l}, @file{.lsp}, or @file{.lisp}.
+ Lisp mode is the major mode for editing programs written in Common
+Lisp or its ancestor dialects. Its mode command is @kbd{M-x
+lisp-mode}. Emacs uses Lisp mode automatically for files whose names
+end in @file{.l}, @file{.lsp}, or @file{.lisp}.
@findex run-lisp
@vindex inferior-lisp-program
diff --git a/lisp/emacs-lisp/lisp-mode.el b/lisp/emacs-lisp/lisp-mode.el
index 59325d647d..99bf1a98c2 100644
--- a/lisp/emacs-lisp/lisp-mode.el
+++ b/lisp/emacs-lisp/lisp-mode.el
@@ -765,7 +765,7 @@ lisp-mode-menu
:help "Run an inferior Lisp process, input and output via buffer `*inferior-lisp*'"]))
(define-derived-mode lisp-mode lisp-data-mode "Lisp"
- "Major mode for editing Lisp code for Lisps other than GNU Emacs Lisp.
+ "Major mode for editing Common Lisp code.
Commands:
Delete converts tabs to spaces as it moves back.
Blank lines separate paragraphs. Semicolons start comments.
next reply other threads:[~2021-06-29 18:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 18:06 João Távora [this message]
2021-06-29 18:16 ` bug#49278: 28.0.50; Lisp Mode is for Common Lisp 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
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
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=87y2asa6lg.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=49278@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).