From: Alan Mackenzie <acm@muc.de>
To: Marti Bolivar <marti.f.bolivar@gmail.com>
Cc: 28098@debbugs.gnu.org
Subject: bug#28098: 26.0.50; bad C fontification
Date: 16 Aug 2017 17:49:48 -0000 [thread overview]
Message-ID: <20170816174948.36467.qmail__10749.2750430994$1502905878$gmane$org@mail.muc.de> (raw)
In-Reply-To: <mailman.13159.1502810889.21957.bug-gnu-emacs@gnu.org>
Hello, Marti.
In article <mailman.13159.1502810889.21957.bug-gnu-emacs@gnu.org> you wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 98 lines --]
> 1. From emacs -Q, open this file:
> https://github.com/zephyrproject-rtos/zephyr/blob/2de59023dc726e61244eb7cca17252294016c65a/subsys/net/lib/http/http_client.c
> 2. Observe incorrect syntax highlighting at beginning of file. Screenshot:
> https://postimg.org/image/tzy8qgjjz/
More precisely, the first ~500 bytes, which consist entirely of comments
and preprocessor directives doesn't get fontified at all.
> (Note that loading a C file with just the #ifdefs and initial
> comment which fail to highlight above doesn't reproduce the issue.)
Thanks. The fact that it's ~500 bytes which don't get fontified suggest
that something is interfering with the first jit-lock chunk. I'll be
looking into it. Give me a bit of time.
> In GNU Emacs 26.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
> of 2017-08-10 built on plop
> Repository revision: 81656add8117e8d1b7faab18b330d0706462b433
> Windowing system distributor 'The X.Org Foundation', version 11.0.11903000
> System Description: Ubuntu 17.04
[ .... ]
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-08-16 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 14:45 bug#28098: 26.0.50; bad C fontification Marti Bolivar
[not found] ` <mailman.13159.1502810889.21957.bug-gnu-emacs@gnu.org>
2017-08-16 17:49 ` Alan Mackenzie [this message]
2017-08-16 20:57 ` Alan Mackenzie
2017-08-21 19:32 ` Marti Bolivar
2017-08-22 17:17 ` Alan Mackenzie
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='20170816174948.36467.qmail__10749.2750430994$1502905878$gmane$org@mail.muc.de' \
--to=acm@muc.de \
--cc=28098@debbugs.gnu.org \
--cc=marti.f.bolivar@gmail.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).