From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#49278: 28.0.50; Lisp Mode is for Common Lisp Date: Tue, 29 Jun 2021 19:25:45 +0100 Message-ID: References: <87y2asa6lg.fsf@gmail.com> <835yxwo7td.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25389"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , 49278@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 29 20:27:09 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lyIRw-0006NI-K3 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 29 Jun 2021 20:27:08 +0200 Original-Received: from localhost ([::1]:56982 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lyIRv-0001qK-Li for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 29 Jun 2021 14:27:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60922) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lyIRp-0001pn-W7 for bug-gnu-emacs@gnu.org; Tue, 29 Jun 2021 14:27:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43747) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lyIRp-0000ZW-PC for bug-gnu-emacs@gnu.org; Tue, 29 Jun 2021 14:27:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lyIRp-0004SB-N8 for bug-gnu-emacs@gnu.org; Tue, 29 Jun 2021 14:27:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 29 Jun 2021 18:27:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 49278 X-GNU-PR-Package: emacs Original-Received: via spool by 49278-submit@debbugs.gnu.org id=B49278.162499116517051 (code B ref 49278); Tue, 29 Jun 2021 18:27:01 +0000 Original-Received: (at 49278) by debbugs.gnu.org; 29 Jun 2021 18:26:05 +0000 Original-Received: from localhost ([127.0.0.1]:55293 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lyIQv-0004Qx-2x for submit@debbugs.gnu.org; Tue, 29 Jun 2021 14:26:05 -0400 Original-Received: from mail-pj1-f51.google.com ([209.85.216.51]:54093) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lyIQt-0004QT-A0 for 49278@debbugs.gnu.org; Tue, 29 Jun 2021 14:26:03 -0400 Original-Received: by mail-pj1-f51.google.com with SMTP id q91so85928pjk.3 for <49278@debbugs.gnu.org>; Tue, 29 Jun 2021 11:26:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dWrdYftc5M7TSDOmNS9USY29VIOK9D8lfYrk/FEVU+o=; b=GxZt3QK5JPv9wlOnh/z7YOxLA9+iNDxwseptMJqvHzel33cejzHPF7XiRgI6ABhK6C 2qhc+FB9grRyZ3V0Fjjt7gjyx3o5OWQMPONOu6zJH6IoyrG2qM/7OeD0YbTdHvrqkH4N o3UwPoh2ZUhnzRaqNZNr4qfNM9zyKeajb66EbK7TJzEL33CSYQgnTXYfRhQjyYbgckGv Fa022wID5H4RJIrPnSPjxeA2ybfjTzdLXklL2GptYK9UjxXtG0LhzkwEPUGCdBBZ0Cy2 cn8nAaqDGxa0oTrkQB2oCyFjyvWRsC7RGblOLTtVnWJPTzC8q6nVkB9neIESmhAxtUhU j3HA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dWrdYftc5M7TSDOmNS9USY29VIOK9D8lfYrk/FEVU+o=; b=PCf7qGCnMAZTRaWfHneRnjdmBhfOHjGncwwcKOSJS0MCXpOalKj6nuOHUlWtUeVF+P RCqlTCX6dgdaGzEHzAK492kTfMJkz6zKr/WxRBZg21f7Q7Hm4ccKclcUsDJNZZTNkfCA Xy3UiNS5+e7piHMVZFBuLGREM7nnmCaz+6IGVu+zSa1zrS+4KjdiFzQNCzuEz9GLBf5K RnrRfRcqNeNzZ/q6CAx1EpMjjVHNT4d40v906bCKRmQ5F/9sgfcCFWU5n8kRFLUUxirq v+6kBFHfv72vc24hOhC7xu2aZ0wpYL1haCtBMj9r0dgvsTZ9mn5Jk2er43m01mtgiI6x R5XA== X-Gm-Message-State: AOAM532MoXinjyDd65plpT67Zv28m4tYVap5w5q3qMoQCiBQ+hS+fglt 3duBVe7827GQ7zCxCk0aJ9BZkJFlML7XVbvI/hY= X-Google-Smtp-Source: ABdhPJzg/iPc5wBxzUYJJa/E8AaVMCI4L66D2QGysJyXjFbNPqUQXvQH/5D4sZ8jOBbgdjZdLWsd1F5ULI5OQT4Knk8= X-Received: by 2002:a17:90a:3983:: with SMTP id z3mr178513pjb.7.1624991157250; Tue, 29 Jun 2021 11:25:57 -0700 (PDT) In-Reply-To: <835yxwo7td.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:209114 Archived-At: On Tue, Jun 29, 2021 at 7:16 PM Eli Zaretskii wrote: > > > From: Jo=C3=A3o T=C3=A1vora > > Date: Tue, 29 Jun 2021 19:06:19 +0100 > > Cc: monnier@iro.umontreal.ca > > > > - 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}. > > This basically doesn't change anything, and the original text does > mention CL. If mentioning the ancestor dialects is important, we > could add that. The point is to make sure that noone is misinformed to think that lisp-mode is a suitable ancestor for, say, scheme-mode or clojure-mode or my-2021-lisp-mode. At the time this was written, all the "general-purpose Lisp dialects" (minus Scheme) would be handled by Lisp mode. But this is just not true anymore. It's for Common Lisp and probably still works decently for, say, the defunct MacLisp and Franz Lisp. So it's not true that this doesn't change anything: it removes an ambiguity. But I'm fine with any other phrasing that also removes this ambiguity. Make a proposal. > > (define-derived-mode lisp-mode lisp-data-mode "Lisp" > > - "Major mode for editing Lisp code for Lisps other than GNU Emacs Lis= p. > > + "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. That's true, I guess. The point is to make sure that no one gets the temptation to derive new Lisp-ish modes based on lisp-mode for languages that have no relation to CL. So what to you say to: "Major mode for editing Common Lisp and historically related Lisps" "Major mode for editing Common Lisp and its ancestors" "Major mode for editing code historically related to Common Lisp" ? Jo=C3=A3o