From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#49278: 28.0.50; Lisp Mode is for Common Lisp Date: Wed, 30 Jun 2021 16:29:24 +0300 Message-ID: <83im1vmqff.fsf@gnu.org> References: <87y2asa6lg.fsf@gmail.com> <835yxwo7td.fsf@gnu.org> <83tulfmsu4.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28641"; mail-complaints-to="usenet@ciao.gmane.io" Cc: joaotavora@gmail.com, 49278@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 30 15:30:15 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 1lyaI9-0007Cu-Ri for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 30 Jun 2021 15:30:13 +0200 Original-Received: from localhost ([::1]:54632 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lyaI7-0007Ol-OG for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 30 Jun 2021 09:30:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:32938) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lyaHy-0007NY-RM for bug-gnu-emacs@gnu.org; Wed, 30 Jun 2021 09:30:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45358) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lyaHy-00013o-In for bug-gnu-emacs@gnu.org; Wed, 30 Jun 2021 09:30:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lyaHy-00040J-B6 for bug-gnu-emacs@gnu.org; Wed, 30 Jun 2021 09:30:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 30 Jun 2021 13:30:02 +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.162505977015334 (code B ref 49278); Wed, 30 Jun 2021 13:30:02 +0000 Original-Received: (at 49278) by debbugs.gnu.org; 30 Jun 2021 13:29:30 +0000 Original-Received: from localhost ([127.0.0.1]:56904 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lyaHS-0003zG-9s for submit@debbugs.gnu.org; Wed, 30 Jun 2021 09:29:30 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:34980) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lyaHQ-0003z3-CE for 49278@debbugs.gnu.org; Wed, 30 Jun 2021 09:29:28 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38250) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lyaHK-0000bf-3d; Wed, 30 Jun 2021 09:29:22 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3567 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lyaHJ-000337-NW; Wed, 30 Jun 2021 09:29:22 -0400 In-Reply-To: (message from Stefan Monnier on Wed, 30 Jun 2021 09:03:01 -0400) 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:209189 Archived-At: > From: Stefan Monnier > Cc: joaotavora@gmail.com, 49278@debbugs.gnu.org > Date: Wed, 30 Jun 2021 09:03:01 -0400 > > > How do you suggest to do that in a concise enough way appropriate for > > a doc string? > > See patch below. I cannot accept that, sorry. At least not yet. I actually still don't understand what practical problem are we trying to solve here. There's no code change, so what the code did until now it will continue to do henceforth. CL and other lisps also won't change by virtue of this patch. So why do we worry what those doc strings say? > The problem is indeed not new, it's the same as 20 years ago. > It's just that noone bothered to fix it. Fix what? what is the problem?