From: Eli Zaretskii <eliz@gnu.org>
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 12:00:04 +0300 [thread overview]
Message-ID: <83fvwjvje3.fsf@gnu.org> (raw)
In-Reply-To: <m2sj0ju6lj.fsf@lifelogs.com>
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Sat, 15 Jun 2013 04:21:44 -0400
>
> On Wed, 12 Jun 2013 05:18:59 +0200 Juanma Barranquero <lekktu@gmail.com> wrote:
>
> JB> If I visit lambda.el as in the example above, and scroll down the
> JB> buffer, I get 26 such failures, always at the same lines (168, 280,
> JB> 364, 432, 489, 538, 581, 619, 654, 686, 715, 742, 767, 791, 813, 834,
> JB> 854, 873, 891, 908, 924, 940, 955, 970, 984 and 998); however, if upon
> JB> visiting the file I go to the end of the buffer and scroll up, I get
> JB> many more failures (about 60) at diferent lines, but also consistently
> JB> the same lines.
>
> Ouch. I don't think I'm doing anything strange in the fontification
> keywords that implement the new prettification functionality, but why
> wasn't this seen before? The scroll behavior probably indicates a
> display engine issue.
What issue would that be?
The problem here is that the composition rule is generated
incorrectly.
next prev parent reply other threads:[~2013-06-15 9:00 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fvwjvje3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14595@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.