From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: message mode loses highlighting
Date: Thu, 26 Jun 2003 07:38:41 -0400 [thread overview]
Message-ID: <4n7k79vzjy.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <m365mt9zsy.fsf@newsguy.com> (Harry Putnam's message of "Wed, 25 Jun 2003 22:24:13 -0700")
On Wed, 25 Jun 2003, reader@newsguy.com wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> Sorry if I didn't make it clear, but I understand that part, my
>> question is why would the tzz-highlighting-install function turn
>> off ALL syntax highlighting in the message buffer? It doesn't do
>> that in an Emacs Lisp buffer, for instance.
>
> I faintly remember having a similar trouble with message mode and
> highlight a long time ago. It went on for quite a while. I posted
> about it but couldn't get it resolved.
>
> I can't remember for sure what the fix was but I think it was
> something simple like having two calls to fontlock in text mode from
> old pieces of init files still lurking about in emacs or
> site-start.el
>
> Might have been two similar or identical hooks to fontlock in text
> mode.
>
> Do you have a text mode hook somewhere calling fontlock?
What I posted is the only customization involving fontlock I have. In
any case, add-keywords should not override any other font locking,
according to the docs, that's why I'm puzzled.
I guess I can look at the message mode source. I'm just so busy right
now that I will probably get to it next year :)
Ted
next prev parent reply other threads:[~2003-06-26 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 15:40 Ted Zlatanov
2003-06-25 23:26 ` Johan Bockgård
2003-06-26 4:42 ` Ted Zlatanov
2003-06-26 5:24 ` Harry Putnam
2003-06-26 11:38 ` Ted Zlatanov [this message]
2003-07-01 12:02 ` Katsumi Yamaoka
2003-07-07 14:36 ` Ted Zlatanov
2003-07-07 16:54 ` Wes Hardaker
2003-07-08 2:34 ` Katsumi Yamaoka
2003-07-10 20:33 ` Ted Zlatanov
2003-07-11 6:50 ` Katsumi Yamaoka
2003-07-11 15:21 ` Ted Zlatanov
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=4n7k79vzjy.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).