all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Mon, 22 Jan 2018 22:21:05 -0800 (PST)	[thread overview]
Message-ID: <4ee1788f-516d-4a1b-8c13-4dc48b3729b8@default> (raw)
In-Reply-To: <132fe701-a996-4708-bf39-4ee95230b8fa@default>

And besides - where do you stop doing this kind of thing?

Do we do something similar for characters that can
be mistaken for a period, in case you use one in an
attempt at dotted-pair syntax?

Do we do something similar for chars that can be
mistaken for a comma, inside backquoted sexps?

Do we do something similar for chars that can be
mistaken for a backquote?  An at-sign?  Ordinary
parentheses?

I really hope you reconsider this.  To me it looks
like an ugly hack that can bring only harm (including
more, not less, confusion), not good.





  reply	other threads:[~2018-01-23  6:21 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ee1788f-516d-4a1b-8c13-4dc48b3729b8@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.