unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 49278@debbugs.gnu.org
Subject: bug#49278: 28.0.50; Lisp Mode is for Common Lisp
Date: Tue, 29 Jun 2021 21:55:36 +0100	[thread overview]
Message-ID: <CALDnm52gX8NU=APJnVy6kWaEbHMnWNphWMXZWjgQks5JysGf9g@mail.gmail.com> (raw)
In-Reply-To: <jwvr1gkflot.fsf-monnier+emacs@gnu.org>

On Tue, Jun 29, 2021 at 9:46 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> >> +  Lisp mode is the major mode for editing programs written in Common
> >> +Lisp or its ancestor dialects.  Its mode command is @kbd{M-x
>
> I think we should remove "or its ancestor dialects" here.

That also works for me, but as you said, it might work reasonably
well for MacLisp etc, too.

> >>  (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.
> > Here I'd prefer to mention CL without un-mentioning the other Lisps.
> > There's no reason to deny they exist or existed.
>
> The question is to describe what this major mode is designed to do.
>
> People who want to look at Maclisp code (or other defunct dialects) will
> probably want to use `lisp-mode` for the simple reason that Maclisp is
> reasonably close to Common Lisp so it's the closest major mode we have
> to offer, but the user should not expect correct handling of Maclisp in
> those places where it differs from Common Lisp, because `lisp-mode` is
> written specifically for Common Lisp and not for Maclisp: compatibility
> with Maclisp has not been taken into account for more than 20
> years, AFAIK.

Yeah, but fair to say MacLisp hasn't evolved tremendously in
those years (and neither has Common Lisp sadly). So I reckon
lisp-mode wouldn't to a terrible job in most MacLisp programs.
And maybe even SLY and a modern Common Lisp compiler
could probably grok MacLisp or Franz Lisp code given sufficient
hand-holding.

Anyway, I hope the main point is across: remove suggestion
that it may be used to derive modes for _new_ lisps unrelated
to Common Lisp.

-- 
João Távora





  reply	other threads:[~2021-06-29 20:55 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 [this message]
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='CALDnm52gX8NU=APJnVy6kWaEbHMnWNphWMXZWjgQks5JysGf9g@mail.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).