From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 32939@debbugs.gnu.org
Subject: bug#32939: 27.0.50; Don't reject confusable quotes, just fontify & mention them in error messages
Date: Tue, 30 Oct 2018 09:12:58 +0200 [thread overview]
Message-ID: <83h8h3lxfp.fsf@gnu.org> (raw)
In-Reply-To: <87woq0i5ks.fsf@gmail.com> (message from Noam Postavsky on Mon, 29 Oct 2018 21:30:43 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: 32939@debbugs.gnu.org
> Date: Mon, 29 Oct 2018 21:30:43 -0400
>
> > However, perhaps we should mention this behavior in "Basic Char
> > Syntax" and the related use of this face in "Faces for Font Lock".
> > WDYT?
>
> I've tried adding some mentions of it in those places (unfilled to
> simplify diff). Though I'm not sure if it makes sense to talk about
> this somewhat obscure case.
I think your text is good, but...
> --- a/doc/lispref/objects.texi
> +++ b/doc/lispref/objects.texi
> @@ -347,7 +347,12 @@ Basic Char Syntax
> characters. However, you must add a backslash before any of the
> characters @samp{()[]\;"}, and you should add a backslash before any
> of the characters @samp{|'`#.,} to avoid confusing the Emacs commands
> -for editing Lisp code. You can also add a backslash before whitespace
> +for editing Lisp code. You should also add a backslash before Unicode
> +characters which resemble the previously mentioned @acronym{ASCII}
> +ones, to avoid confusing people reading your code. Emacs will
> +highlight some non-escaped commonly confused characters such as
> +@samp{‘} to encourage this.
> + You can also add a backslash before whitespace
^^^^^^^^^^^^^^^^^^^^^^^^
What's the deal with this large whitespace stretch?
Thanks.
next prev parent reply other threads:[~2018-10-30 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 23:58 bug#32939: 27.0.50; Don't reject confusable quotes, just fontify & mention them in error messages Noam Postavsky
2018-10-05 8:44 ` Eli Zaretskii
2018-10-24 22:25 ` Noam Postavsky
2018-10-27 9:48 ` Eli Zaretskii
2018-10-30 1:30 ` Noam Postavsky
2018-10-30 7:12 ` Eli Zaretskii [this message]
2019-11-17 8:42 ` Lars Ingebrigtsen
2019-11-27 19:42 ` Noam Postavsky
2019-11-28 23:25 ` 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=83h8h3lxfp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32939@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/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).