From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ista Zahn Newsgroups: gmane.emacs.bugs Subject: bug#30217: Ambiguity in NEWS in emacs-26.0.91 Date: Fri, 2 Feb 2018 17:14:12 -0500 Message-ID: References: <20180122221743.GB4888@ACM> <5074511f-b3b3-45aa-80b4-130be08f30ec@default> <87efmho17g.fsf@users.sourceforge.net> <4c079376-7659-4962-aa73-39a4b4ed76e0@default> <878tcpnyio.fsf@users.sourceforge.net> <132fe701-a996-4708-bf39-4ee95230b8fa@default> <871sigohv9.fsf@users.sourceforge.net> <1a1fbaea-f291-414d-aaef-bf41ea4a5873@default> <87y3komb9o.fsf@users.sourceforge.net> <87vafsm8e2.fsf@users.sourceforge.net> <87po5ukmkt.fsf@users.sourceforge.net> <60dfc051-9871-488e-a942-7d10519bd661@default> <29f2629e-35dd-4c6d-859e-d5851e3f9125@default> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c1ce0a24897ee0564420854" X-Trace: blaine.gmane.org 1517609612 29171 195.159.176.226 (2 Feb 2018 22:13:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 2 Feb 2018 22:13:32 +0000 (UTC) Cc: Alan Mackenzie , 30217@debbugs.gnu.org, Noam Postavsky To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Feb 02 23:13:28 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ehja2-0006Do-4c for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 Feb 2018 23:13:10 +0100 Original-Received: from localhost ([::1]:36685 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehjc1-0000kb-Iu for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 Feb 2018 17:15:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehjbu-0000k5-W6 for bug-gnu-emacs@gnu.org; Fri, 02 Feb 2018 17:15:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehjbr-000342-0B for bug-gnu-emacs@gnu.org; Fri, 02 Feb 2018 17:15:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:46764) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ehjbq-00033P-Qd for bug-gnu-emacs@gnu.org; Fri, 02 Feb 2018 17:15:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ehjbq-0000Ha-B8 for bug-gnu-emacs@gnu.org; Fri, 02 Feb 2018 17:15:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ista Zahn Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 Feb 2018 22:15:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30217 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 30217-submit@debbugs.gnu.org id=B30217.15176096621021 (code B ref 30217); Fri, 02 Feb 2018 22:15:02 +0000 Original-Received: (at 30217) by debbugs.gnu.org; 2 Feb 2018 22:14:22 +0000 Original-Received: from localhost ([127.0.0.1]:54660 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ehjbB-0000GP-Ml for submit@debbugs.gnu.org; Fri, 02 Feb 2018 17:14:21 -0500 Original-Received: from mail-lf0-f42.google.com ([209.85.215.42]:38495) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ehjb9-0000GC-2P for 30217@debbugs.gnu.org; Fri, 02 Feb 2018 17:14:19 -0500 Original-Received: by mail-lf0-f42.google.com with SMTP id g72so33594280lfg.5 for <30217@debbugs.gnu.org>; Fri, 02 Feb 2018 14:14:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+iBaCbObvLAPnVOWPiYGmJaCR0NbvtEQr5hPFwswP4k=; b=J3Ww4O3v/Dm32+xHQZSXeUcyTuveWVvOuHrSn9CB2vFgTioctAh1eQYn535Dj7fyTK 0W7qpch7y1c7Vxp71rt8vn69vGIKEk6x/yeNAaaL1b6TRrIaOmVA0v8fFCd6Ya8ANgjo 4Zix9A7gFMS4DTQQRTez+rhR6Wh9DF0oRSdNDcdY811HD5EMIsxq7SKFhJ4x17iUXckB h7BdLrZOOdVe8RzhIRbrEnlnjV7PwE9TENB/pu5YycIpHdKiaHOwM4Cq15DocxZ7DQhW 59MZFWcm0Ru1gejUc2f9HhxaBdI8k4LvpsHi+FhBNZwZPi6kYt01wzJ8fKH61Rmg0Ira Bzhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+iBaCbObvLAPnVOWPiYGmJaCR0NbvtEQr5hPFwswP4k=; b=jVy1En6+qGrFgrRg6zgdc4BvwSwrLoePtIhc0mspLWvo2JpAheuadUJjH1zLOFCanL qaPbIuhOUios3RNLWP4MBNvLDSVW0I7o3Yjs7vzsIu7qDGO5IwW6sdjJF87h8++kvrJs r7Ry7lIpQS7dn77L6mLLSE5j7d2zvevjC85zHTsowySkWMIDU7YdIELpS9koKjuUkfRc r3vsu17qQc5r7MPCAxMh59lnQSSe0LNg6CIErec5lBy2PJj6lKCdB/hqnOS2lbH18Sgn Vct96DtATDZpIjMb5xejDenWxfMrFoVWi794jedJa/0ONJORal3b691RniV4ifFm2eS3 wY1Q== X-Gm-Message-State: AKwxyter4eEuU9W8nNy0R2iyWLMEVZFOQYqSrmJJvgoDm6xAKNLKusDT tquUl9Ka9M6Gqa+6LSK6OCvT7UYY4IX2jn1+f/I= X-Google-Smtp-Source: AH8x224LWjZj93xj7NVlkG0jVd58tTBmX0jAaxeANb9mD3iAG3+JZiXfJOLEB161wc0aJfEEDVb08RV1XgUZpAGye+k= X-Received: by 10.25.83.198 with SMTP id h67mr26033920lfl.135.1517609653145; Fri, 02 Feb 2018 14:14:13 -0800 (PST) Original-Received: by 10.25.41.134 with HTTP; Fri, 2 Feb 2018 14:14:12 -0800 (PST) Original-Received: by 10.25.41.134 with HTTP; Fri, 2 Feb 2018 14:14:12 -0800 (PST) In-Reply-To: <29f2629e-35dd-4c6d-859e-d5851e3f9125@default> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:142821 Archived-At: --94eb2c1ce0a24897ee0564420854 Content-Type: text/plain; charset="UTF-8" On Feb 2, 2018 4:39 PM, "Drew Adams" wrote: > > Sorry, but it's not clear to me. Is this being abandoned > > completely (I hope so), or is it just being postponed to > > Emacs 27? > > It's currently only postponed to Emacs 27, I suggest you bring it up > in emacs-devel if you think we should get rid of it. Since we simply > disagree about this, I don't think further dialogue here will help > anything. I think you should bring it up, and I think you should have from the beginning. This is not just about fixing a bug. You're the one who is, in effect, proposing a change to Lisp. This is not normal Lisp behavior. This is a far cry from quote and backquote, comma and period, all of which are quite traditional for Lisp. These are ordinary symbol-constituent characters, and should not be handled in the way you've implemented. (I wanted to say "suggested", but you didn't suggest it to emacs-devel; you just implemented it - in a bug thread, no less.) I'm nobody in this community, but in case it means anything I agree completely with Drew. This isn't a bug fix, but a language change that needs to be carefully thought out and discussed. --94eb2c1ce0a24897ee0564420854 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Feb 2, 2018 4:39 PM, "Drew Adams" <drew.adams@oracle.com> wrote:
> > Sorr= y, but it's not clear to me.=C2=A0 Is this being abandoned
> > completely (I hope so), or is it just being postponed to
> > Emacs 27?
>
> It's currently only postponed to Emacs 27, I suggest you bring it = up
> in emacs-devel if you think we should get rid of it. Since we simply > disagree about this, I don't think further dialogue here will help=
> anything.

I think you should bring it up, and I think you should have
from the beginning.=C2=A0 This is not just about fixing a bug.

You're the one who is, in effect, proposing a change to Lisp.

This is not normal Lisp behavior.=C2=A0 This is a far cry from
quote and backquote, comma and period, all of which are quite
traditional for Lisp.

These are ordinary symbol-constituent characters, and should
not be handled in the way you've implemented.=C2=A0 (I wanted to
say "suggested", but you didn't suggest it to emacs-devel; you just implemented it - in a bug thread, no less.)
=

I'm nobody in this community, but in case it mean= s anything I agree completely with Drew. This isn't a bug fix, but a la= nguage change that needs to be carefully thought out and discussed.<= br style=3D"font-family:sans-serif">



--94eb2c1ce0a24897ee0564420854--