From: npostavs@users.sourceforge.net
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Andrew Hyatt <ahyatt@gmail.com>,
4030@debbugs.gnu.org, era+emacsbugs@iki.fi
Subject: bug#4030: forward-sexp parses character literal ?; as comment
Date: Fri, 12 May 2017 22:55:29 -0400 [thread overview]
Message-ID: <871srtjwim.fsf@users.sourceforge.net> (raw)
In-Reply-To: <jwvh9crcebx.fsf-monnier+bug#4030@gnu.org> (Stefan Monnier's message of "Sat, 18 Jun 2016 00:31:39 -0400")
tags 4030 wontfix
close 4030
quit
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Does anyone have any further thoughts? It wasn't clear to me from this
>> discussion whether there was any consensus that this was actually a bug
>> or not.
>
>
> So we can either:
[...]
> - deprecate ?; and friends, probably adding font-lock highlights to help
> spot the problematic cases, and maybe changing the Lisp reader code to
> warn about those things as well (with intention to remove support for
> them).
Since we now emit such warnings, I'm closing this bug as wontfix.
See also https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20852
[1: c2bbdc3316]: 2017-05-01 20:39:10 +0200
Warn about missing backslashes during load
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=c2bbdc3316487e34eba1470dd059c0c290431e00
[2: 3c4c8ca06e]: 2017-05-07 13:22:34 +0200
Fix all unescaped character literals
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=3c4c8ca06e3306ccbcd07e354eb51abe53b52d22
prev parent reply other threads:[~2017-05-13 2:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 12:07 bug#4030: forward-sexp parses character literal ?; as comment era+emacsbugs
2009-08-04 12:43 ` martin rudalics
2009-08-05 8:17 ` era+emacsbugs
2009-08-05 14:29 ` martin rudalics
2009-08-06 8:55 ` era+emacsbugs
2009-08-06 18:51 ` Stefan Monnier
2009-08-07 13:01 ` martin rudalics
2009-08-10 19:59 ` Stefan Monnier
2009-08-11 9:17 ` martin rudalics
2016-06-18 3:47 ` Andrew Hyatt
2016-06-18 4:31 ` Stefan Monnier
2017-05-13 2:55 ` npostavs [this message]
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=871srtjwim.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=4030@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=era+emacsbugs@iki.fi \
--cc=monnier@IRO.UMontreal.CA \
/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).