From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Howard Melman Newsgroups: gmane.emacs.bugs Subject: bug#54964: 28.1; mistatement in NEWS about read-extended-command-predicate Date: Sat, 16 Apr 2022 10:20:57 -0400 Message-ID: References: <4DA6706F-6B98-4CA5-B1A5-EAFBDAB3125F@gmail.com> <83mtgl1qoi.fsf@gnu.org> <877d7pfkec.fsf@gnus.org> <838rs51ery.fsf@gnu.org> <87tuate1jr.fsf@gnus.org> <835yn91dzi.fsf@gnu.org> <83zgklyvxp.fsf@gnu.org> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19451"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 54964@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 16 16:22:17 2022 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 1nfjJY-0004su-Ka for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 Apr 2022 16:22:16 +0200 Original-Received: from localhost ([::1]:47174 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nfjJX-0004ZK-6u for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 Apr 2022 10:22:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45134) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nfjJK-0004Yy-Ud for bug-gnu-emacs@gnu.org; Sat, 16 Apr 2022 10:22:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40102) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nfjJK-000245-I1 for bug-gnu-emacs@gnu.org; Sat, 16 Apr 2022 10:22:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nfjJK-00016b-Cc for bug-gnu-emacs@gnu.org; Sat, 16 Apr 2022 10:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Howard Melman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 16 Apr 2022 14:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54964 X-GNU-PR-Package: emacs Original-Received: via spool by 54964-submit@debbugs.gnu.org id=B54964.16501188654175 (code B ref 54964); Sat, 16 Apr 2022 14:22:02 +0000 Original-Received: (at 54964) by debbugs.gnu.org; 16 Apr 2022 14:21:05 +0000 Original-Received: from localhost ([127.0.0.1]:33999 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nfjIP-00015H-I2 for submit@debbugs.gnu.org; Sat, 16 Apr 2022 10:21:05 -0400 Original-Received: from mail-qk1-f174.google.com ([209.85.222.174]:41704) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nfjIO-00014M-9t for 54964@debbugs.gnu.org; Sat, 16 Apr 2022 10:21:04 -0400 Original-Received: by mail-qk1-f174.google.com with SMTP id s70so1610798qke.8 for <54964@debbugs.gnu.org>; Sat, 16 Apr 2022 07:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sYkBiAZZVQgtHzP9qA1AJrtQfgLn4x1Vyn/g07P9u3Y=; b=XWxK2VycsHYe88Z9VT2Uvr9IAUSarauC/hGmjk2ZkyyMQ18A6L+KrP84HYMKCzrESP +8QQoYODXgq1m+Zw9K9Aj7lQhwAKsSR/dA1SJpzrdXkAS28OK6QE/Fbpj6qSdS8jBmCu 6ahoFf3WBO8Qyt7v49/ls/urnesuF0lf17G8eCPROv1H6KEy6ilbkG7GsumtusG4bw6S oQ5zStds7fQTgJnarWBhK++RXGb1AyEJ6SjWafxECiLY30PWWmV4ZT9E1deEu+5tBn+O 0n27c7Bsvd4B7qHA0j4wdoIHSlh5zudTWH6rbiv4ByNZVAQEOS4LAiTaWt9Kwd3BS9dq nYPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sYkBiAZZVQgtHzP9qA1AJrtQfgLn4x1Vyn/g07P9u3Y=; b=7vp7v7t4RfW2Ptx1rBWs7ci0azXY4n0t8ddQa5mUo8EYYkva1hE6A6W53at8IspfHG Wwaf8t4otC3XD7ZIbfEb+Vb1SaiIK44HGsRgliloX0nP4Xb3Iu7w9MPXO19cPNGb79er f/Y8cY4Db9Rh7MKwe7bR2gQB/X9IAluCPDZlylXsbCLFIVREx/LWPhQdXOS5PKSwmu/m b2tRitKUwxzlpLdIR5wVg+qcfkfKvLPtTqqOBvThHVLTQLGPbL9zw6LZWP20NmGgDjxr 9mRuyQoNS93WdCKV7oB86jvh48ZGKkmo/B8Z5EY7xK88kIg7Sj4Co9rbBkZPgk2ftepZ ijfQ== X-Gm-Message-State: AOAM532JvZNglHIaEM7ZUIJcsB3rCPshvWOHOPB0FEd8bmkxHynYycXy 1awW1tvtrsPALc2flXJ7vrQ= X-Google-Smtp-Source: ABdhPJxojgKTUDkh8Xxe6N2kCdwYLunc7B4l+PaZfGyinOUUobjM1hDZ8XyWxpeO3o46+BneI6UR1Q== X-Received: by 2002:a05:620a:178f:b0:699:90a7:ffdf with SMTP id ay15-20020a05620a178f00b0069990a7ffdfmr2046897qkb.523.1650118858727; Sat, 16 Apr 2022 07:20:58 -0700 (PDT) Original-Received: from smtpclient.apple (pool-108-26-204-101.bstnma.fios.verizon.net. [108.26.204.101]) by smtp.gmail.com with ESMTPSA id f6-20020ac859c6000000b002ee0948f1aesm4383127qtf.72.2022.04.16.07.20.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Apr 2022 07:20:58 -0700 (PDT) In-Reply-To: <83zgklyvxp.fsf@gnu.org> X-Mailer: Apple Mail (2.3654.120.0.1.13) 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:229988 Archived-At: On Apr 16, 2022, at 9:55 AM, Eli Zaretskii wrote: >> I think adding to the end something like: "from M-x (though >> they are used by M-S-x which see below)". would clarify it. > > There's no real way for us to clarify NEWS entries after the > corresponding Emacs version was released, since we cannot > retroactively modify released versions, and Emacs 28.2 will have its > own section in NEWS, separate from Emacs 28.1. And since this is > about something that is not even explicitly stated in NEWS, but your > inference from what is written there, I don't see an urgent need to > try to find some way of clarifying it. The downside, I presume, is > that someone else could perhaps be led to the same erroneous > conclusion as you were. We'll have to live with that, I guess. I mean you could clarify the 28.1 entry and then anyone that skipped 28.1 and went to a later version would benefit. This is obviously minor. I don't need the clarification, I reported it to benefit anyone else that might. Howard