unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Stefan Kangas" <stefan@marxist.se>,
	"João Távora" <joaotavora@gmail.com>,
	"49278@debbugs.gnu.org" <49278@debbugs.gnu.org>
Subject: bug#49278: [External] : bug#49278: 28.0.50; Lisp Mode is for Common Lisp
Date: Mon, 27 Sep 2021 22:06:40 -0400	[thread overview]
Message-ID: <jwvr1d9zd87.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488F39277DEDB206C7C4ABCF3A79@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Mon, 27 Sep 2021 23:24:07 +0000")

> No.  I was saying that I don't see why we should
> say that "lisp-mode is only for Common Lisp".

AFAIK nobody has suggested to say "only Common Lisp".
The suggested text was:

    +  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}.

>> No, that's the thing, it's a Common Lisp mode, not just "any Lisp" mode.
> Then call it such, if you're sure it's useful
> only for Common Lisp.

Again, where does that "only" come from?  The thing I think we should
say clearly is that it's a major mode for Common Lisp.  The current
text:

    -  Lisp mode is the major mode for editing programs written in
    -general-purpose Lisp dialects, such as Common Lisp.  Its mode command

is just misleading since you'll probably be quite disappointed if you
try to use it with most other "general-purpose Lisp dialects" (such as
Clojure or Scheme).  Among the non-general purpose Lisp languages,
I think it can be tolerably for AutoCAD's Lisp (tho `emacs-lisp-mode`
would probably work about as well), but probably not for DSSSL (and even
less for XSLT, tho whether it'd still qualify as Lisp is not so clear).

>> Why should the name of the major mode be relevant to this discussion?
> Why indeed.  `irrelevant-mode'? `mystery-mode'?
> I'd like to call it `fortran-mode', but I guess
> that's out.

The major mode I use for ELisp is called `emacs-lisp-mode`, the major
mode I use for OCaml is `tuareg-mode`, the major mode I use for C is
`sm-c-mode`.  The most popular major mode for Perl is arguably
`cperl-mode`.  It's common for major modes's names to be related yet not
identical to the language they support.


        Stefan






  parent reply	other threads:[~2021-09-28  2:06 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
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 [this message]
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=jwvr1d9zd87.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=49278@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=joaotavora@gmail.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 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).