unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28349@debbugs.gnu.org, Tom Tromey <tom@tromey.com>
Subject: bug#28349: 26.0.50; compilation mode syntax highlighting incorrect
Date: Sun, 10 Sep 2017 19:33:44 +0100	[thread overview]
Message-ID: <CAPM58oiO3qWNytq0npJM-0UGKFcccQ+dZH+SHs0axf6k0apjow@mail.gmail.com> (raw)
In-Reply-To: <87bmmi8o6i.fsf@bapiya>

On 10 September 2017 at 18:21, Tom Tromey <tom@tromey.com> wrote:
> Eli> No comments, so I fixed this bug by resurrecting the lost function,
> Eli> and I'm marking the bug done.
>
> Thanks.  I think this was the right thing to do.
>
> Tom

Thanks. There seems to be another similar issue remaining.
Font-locking still fails for some lines "at random". This time the errors are

Error during redisplay: (jit-lock-function 94586) signaled
(args-out-of-range 0 3)
Error during redisplay: (jit-lock-function 284681) signaled
(args-out-of-range 0 3)
Error during redisplay: (jit-lock-function 285181) signaled
(args-out-of-range 0 3)
etc.





  reply	other threads:[~2017-09-10 18:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 19:21 bug#28349: 26.0.50; compilation mode syntax highlighting incorrect Richard Copley
2017-09-05 15:26 ` Eli Zaretskii
2017-09-09 18:05   ` Eli Zaretskii
2017-09-10 17:21     ` Tom Tromey
2017-09-10 18:33       ` Richard Copley [this message]
2017-09-10 19:42         ` Eli Zaretskii
2017-09-10 19:57           ` Richard Copley
2017-09-10 22:41             ` Richard Copley
2017-09-11 14:53               ` Eli Zaretskii
2017-09-11 15:33                 ` Richard Copley
2017-09-11 16:56                   ` Eli Zaretskii
2017-09-11 19:51                     ` Richard Copley
2017-09-16 18:30                       ` Richard Copley
2017-09-16 18:37                         ` Eli Zaretskii
2017-09-16 18:49                           ` Richard Copley

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=CAPM58oiO3qWNytq0npJM-0UGKFcccQ+dZH+SHs0axf6k0apjow@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=28349@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=tom@tromey.com \
    /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).