unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: 4030@debbugs.gnu.org, era+emacsbugs@iki.fi
Subject: bug#4030: forward-sexp parses character literal ?; as comment
Date: Sat, 18 Jun 2016 00:31:39 -0400	[thread overview]
Message-ID: <jwvh9crcebx.fsf-monnier+bug#4030@gnu.org> (raw)
In-Reply-To: <m21t3vb1l0.fsf@Andrews-MacBook-Pro.local> (Andrew Hyatt's message of "Fri, 17 Jun 2016 23:47:07 -0400")

> 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.

With the support for syntax-fontification "on-the-fly" within
forward-sexp, we could actually make forward-sexp handle those
cases correctly nowadays.

So we can either:
- make it work with a syntax-propertize-function.  Not sure it's worth
  the cost.
- 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).
- keep on living with this occasional problem.


        Stefan





  reply	other threads:[~2016-06-18  4:31 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 [this message]
2017-05-13  2:55                   ` npostavs

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='jwvh9crcebx.fsf-monnier+bug#4030@gnu.org' \
    --to=monnier@iro.umontreal.ca \
    --cc=4030@debbugs.gnu.org \
    --cc=ahyatt@gmail.com \
    --cc=era+emacsbugs@iki.fi \
    /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).