From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 49278@debbugs.gnu.org
Subject: bug#49278: 28.0.50; Lisp Mode is for Common Lisp
Date: Wed, 30 Jun 2021 16:58:53 +0100 [thread overview]
Message-ID: <CALDnm53v7_c9mgoevGsaC+igYJfScpoTAZeOg0hkcxU=QWWnVw@mail.gmail.com> (raw)
In-Reply-To: <837dibmjo9.fsf@gnu.org>
On Wed, Jun 30, 2021 at 4:55 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: João Távora <joaotavora@gmail.com>
> > Date: Wed, 30 Jun 2021 15:54:39 +0100
> > Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 49278@debbugs.gnu.org
> >
> > > Lisp mode is the major mode for editing programs written in
> > > general-purpose Lisp dialects, such as Common Lisp.
> >
> > But that is false :-) Scheme, Clojure and Phil's Fennel are two
> > "general purpose Lisp dialects" that are not at all well suited
> > to be edited with lisp-mode in Emacs.
>
> Would it be okay to mention those 3 exceptions explicitly?
I guess, but there are probably many more Lisp dialects
out there. It's just more economical to state it the other way
round, right? But with the change to the lisp-mode docstring
I think we're already in a better place.
(As you may guess, I still don't see what the problem in
saying "for editing Common Lisp and languages directly related
to it" is. It's short and accurate.
Though even shorter and more accurate, as Stefan pointed out is
"for editing Common Lisp".)
João Távora
next prev parent reply other threads:[~2021-06-30 15:58 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 [this message]
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='CALDnm53v7_c9mgoevGsaC+igYJfScpoTAZeOg0hkcxU=QWWnVw@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=49278@debbugs.gnu.org \
--cc=eliz@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).