From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Alan Mackenzie <acm@muc.de>, 30217@debbugs.gnu.org
Subject: bug#30217: Ambiguity in NEWS in emacs-26.0.91
Date: Fri, 2 Feb 2018 13:37:57 -0800 (PST) [thread overview]
Message-ID: <29f2629e-35dd-4c6d-859e-d5851e3f9125@default> (raw)
In-Reply-To: <CAM-tV-_4Jr4RS6jCkg9DHJb7L-fuJ4CjEOxqc0VXM0WJMneLQw@mail.gmail.com>
> > 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.)
next prev parent reply other threads:[~2018-02-02 21:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 22:17 bug#30217: Ambiguity in NEWS in emacs-26.0.91 Alan Mackenzie
2018-01-22 22:42 ` Drew Adams
2018-01-23 0:42 ` Noam Postavsky
2018-01-23 0:56 ` Drew Adams
2018-01-23 1:40 ` Noam Postavsky
2018-01-23 6:07 ` Drew Adams
2018-01-23 6:21 ` Drew Adams
2018-01-23 12:54 ` Noam Postavsky
2018-01-23 15:53 ` Drew Adams
2018-01-23 23:00 ` Noam Postavsky
2018-01-23 23:19 ` Drew Adams
2018-01-24 0:02 ` Noam Postavsky
2018-01-28 15:52 ` Noam Postavsky
2018-02-02 18:52 ` Drew Adams
2018-02-02 19:08 ` Noam Postavsky
2018-02-02 21:37 ` Drew Adams [this message]
2018-02-02 22:14 ` Ista Zahn
2018-02-02 22:35 ` Noam Postavsky
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=29f2629e-35dd-4c6d-859e-d5851e3f9125@default \
--to=drew.adams@oracle.com \
--cc=30217@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=npostavs@users.sourceforge.net \
/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).