From: Dmitry Gutov <dgutov@yandex.ru>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Katsumi Yamaoka' <yamaoka@jpl.org>, 13816@debbugs.gnu.org
Subject: bug#13816: 24.3.50; turn-on-font-lock doesn't turn it on
Date: Tue, 26 Feb 2013 10:45:48 +0400 [thread overview]
Message-ID: <87fw0jd143.fsf@yandex.ru> (raw)
In-Reply-To: <84D5B63784C44412BF9B94C63C729AB4@us.oracle.com> (Drew Adams's message of "Mon, 25 Feb 2013 22:05:51 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
>> > Recently turn-on-font-lock set to some hook turns font-lock
>> > on but turns it off immediately regardless of the value of
>> > global-font-lock-mode. Here's a recipe:
>>
>> > emacs -Q
>> > Eval: (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
>> > and visit some .el file.
>>
>> Works fine on the trunk right now. Can you confirm it was
>> fixed if you try a recent enough build?
>
> The recent font-lock breakage is still there - it still does not work as of this
> trunk build, today:
>
> In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
> of 2013-02-25 on ODIEONE
> Bzr revision: 111879 yamaoka@jpl.org-20130225224731-cv9gznq5nqf3ei7g
> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> Configured using:
> `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
> -IC:/Devel/emacs/build/include --ldflags -LC:/Devel/emacs/build/lib'
>
> In particular, see bug #13767 (no `&optional' highlighting) and bug #13755 (see
> screenshots).
>
> However, bug #13751 seems to be fixed, at first sight, at least.
I also experienced font-lock-mode not turning on, and it was caused by
whitespace-mode. That part has been fixed in revision 111881.
next prev parent reply other threads:[~2013-02-26 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 2:02 bug#13816: 24.3.50; turn-on-font-lock doesn't turn it on Katsumi Yamaoka
2013-02-26 3:01 ` Stefan Monnier
2013-02-26 6:05 ` Drew Adams
2013-02-26 6:45 ` Dmitry Gutov [this message]
2013-02-26 7:29 ` Katsumi Yamaoka
2013-02-26 7:51 ` Katsumi Yamaoka
2013-02-26 14:04 ` Stefan Monnier
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=87fw0jd143.fsf@yandex.ru \
--to=dgutov@yandex.ru \
--cc=13816@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=yamaoka@jpl.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.