From: Ted Zlatanov <tzz@lifelogs.com>
To: 14595@debbugs.gnu.org
Subject: bug#14595: Erroneous composition of lambda in emacs-lisp buffers with prog-prettify-symbols enabled
Date: Sat, 15 Jun 2013 20:13:28 -0400 [thread overview]
Message-ID: <m2fvwiud3r.fsf@lifelogs.com> (raw)
In-Reply-To: <CAAeL0STXZWfhOYS24ta2jF=VtAQNKdY+eAjvX99f_nqDF97fHw@mail.gmail.com>
On Sat, 15 Jun 2013 19:49:10 +0200 Juanma Barranquero <lekktu@gmail.com> wrote:
JB> In other words, this simple patch fixes the problem:
JB> === modified file 'lisp/progmodes/prog-mode.el'
JB> --- lisp/progmodes/prog-mode.el 2013-06-06 21:32:13 +0000
JB> +++ lisp/progmodes/prog-mode.el 2013-06-15 17:47:50 +0000
JB> @@ -77,7 +77,7 @@
JB> '(?w) '(?. ?\\))))
JB> (if (or (memq (char-syntax (or (char-before start) ?\ )) syntaxes)
JB> (memq (char-syntax (or (char-after end) ?\ )) syntaxes)
JB> - (nth 8 (syntax-ppss)))
JB> + (nth 8 (save-match-data (syntax-ppss))))
JB> ;; No composition for you. Let's actually remove any composition
JB> ;; we may have added earlier and which is now incorrect.
JB> (remove-text-properties start end '(composition))
Nice catch.
JB> but, it would still be nice to know why syntax-ppss destroys
JB> (match-data 0) in some lines and not all of them.
I took this code out of `perl-mode' but didn't write it. I hope someone
else can answer.
Ted
next prev parent reply other threads:[~2013-06-16 0:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 3:18 bug#14595: Erroneous composition of lambda in emacs-lisp buffers with prog-prettify-symbols enabled Juanma Barranquero
2013-06-15 8:21 ` Ted Zlatanov
2013-06-15 9:00 ` Eli Zaretskii
2013-06-15 9:12 ` Eli Zaretskii
2013-06-15 17:35 ` Juanma Barranquero
2013-06-15 17:49 ` Juanma Barranquero
2013-06-15 20:51 ` Juanma Barranquero
2013-06-16 0:13 ` Ted Zlatanov [this message]
2013-06-16 0:53 ` Stefan Monnier
2013-06-16 1:19 ` Juanma Barranquero
2013-06-16 1:32 ` Juanma Barranquero
2013-06-16 0:17 ` Ted Zlatanov
2013-06-16 2:50 ` Eli Zaretskii
2013-06-16 3:01 ` Juanma Barranquero
2013-06-16 9:27 ` Ted Zlatanov
2013-06-16 16:17 ` Eli Zaretskii
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=m2fvwiud3r.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=14595@debbugs.gnu.org \
--cc=bug-gnu-emacs@gnu.org \
/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).