unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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 19:35:38 +0200	[thread overview]
Message-ID: <CAAeL0SRK-TT-RigMexmEOYBXaao1TBVUw=q0-0-E0mmaeMEMog@mail.gmail.com> (raw)
In-Reply-To: <83ehc3viss.fsf@gnu.org>

On Sat, Jun 15, 2013 at 11:12 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> The incorrect display happens when the underlined part below
>
>       (compose-region start end (cdr (assoc (match-string 0) alist)))))
>                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> is nil.  When that happens, (match-string 0) is "(", the left
> parenthesis, not the expected "lambda".

The call to syntax-ppss inside prog--prettify-font-lock-compose-symbol
is altering the match-string data. I saved (match-string 0) in the
let* as ms0, and then for the erroneous lines I get this log:

start = 2507 / end = 2513 / (match-string 0) = #("(" 0 1 (fontified
t)) / ms0 = #("lambda" 0 6 (fontified t)) / alist = (("lambda" . 955))

so it was correct when the function was called. Then I wrapped the
syntax-ppss call inside save-match-data and the bug disappears.

> I hope fontification gurus will be able to tell us why this could
> happen.

Yep.





  reply	other threads:[~2013-06-15 17:35 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 [this message]
2013-06-15 17:49         ` Juanma Barranquero
2013-06-15 20:51           ` Juanma Barranquero
2013-06-16  0:13           ` Ted Zlatanov
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='CAAeL0SRK-TT-RigMexmEOYBXaao1TBVUw=q0-0-E0mmaeMEMog@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=14595@debbugs.gnu.org \
    --cc=eliz@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).