Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: message mode loses highlighting
Date: Thu, 10 Jul 2003 16:33:39 -0400	[thread overview]
Message-ID: <4nznjmyvdo.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <b9ysmph21cl.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 08 Jul 2003 11:34:18 +0900")

On Tue, 08 Jul 2003, yamaoka@jpl.org wrote:
> I'm well aware of that.  How did you use to turn on font-lock in
> a messege buffer (before using it)?  AFAIK, Gnus doesn't turn on
> font-lock for the message-mode by default, except for XEmacs.

I have

(global-font-lock-mode t)

in my .emacs, and it affects message-mode as well I think.

> You are right.  The tzz- function will surely turn on font-lock
> for the *text-mode* and it will be still turned on for the
> message-mode.  Even so, the message-font-lock-keywords variable
> will still be ignored.  What you should do is to add the
> following hook in order to turn on font-lock again for the
> *message-mode*.  For that purpose, it is necessary to use
> `(font-lock-mode 1)' rather than `turn-on-font-lock' since
> t-o-f-l does nothing if font-lock is already turned on:
> 
> (add-hook 'message-mode-hook (lambda nil (font-lock-mode 1)))

When I do M-x font-lock-mode in a message-mode buffer it disables
font-lock.  Running it again re-enables font-lock.

M-: (font-lock-mode 1) in a message-mode buffer after the
tzz-highlighting-install function has no effect (but it returns t).
The buffer remains without highlighting.  Adding it to the
message-mode-hook as a lambda function has no effect, either.

Basically, my problem is that tzz-highlighting-install should work,
and works in all other modes, but for message-mode it turns font-lock
off.  font-lock, however, still thinks it's on!  So maybe the
message-mode highlighting keywords are somehow affected by the
font-lock-add-keywords statement.

> P.S.
> Sorry for my funny English.  I am a sophisticated writer in
> Japanese, but not in English. ;-)

No problem, I appreciate your help greatly.  I don't know if I'll get
the characters right, since I don't speak Japanese, but here's a try: 
どうもarigataう :) 

I couldn't figure out a way to input "ari" or "gata" with the
japanese-hiragana input method.

Ted



  reply	other threads:[~2003-07-10 20:33 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
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 [this message]
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=4nznjmyvdo.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).