message-mode, compilation, XEmacs 21.4.14

message-mode, compilation, XEmacs 21.4.14

[Chris Green]

Hey folks,

I'm finally getting around to updating to NoGnus, I've run into a
problem if I byte-compile message.el, as soon as I enter a *mail*
buffer, after displaying an *Article*, font-lock becomes becomes
broken as soon as I type some text

(extent-at (point)) returns nil though if I don't type on the line, it
does return useful information.

font-lock-defaults is currently set to nil.

http://thread.gmane.org/gmane.emacs.gnus.general/53254 describes what
I'm seeing but the hook solution doesn't help me out here b/c the
font-lock-defaults are nil I believe.

Any ideas what from *Article* font-lock is clobbering *mail*
font-lock?
-- 
Chris Green <cmg@dok.org>
Warning: time of day goes back, taking countermeasures.

Re: message-mode, compilation, XEmacs 21.4.14

[Kai Grossjohann]

Chris Green <cmg@dok.org> writes:

> http://thread.gmane.org/gmane.emacs.gnus.general/53254 describes what
> I'm seeing but the hook solution doesn't help me out here b/c the
> font-lock-defaults are nil I believe.

Hm?  What does the solution of explicitly turn font-lock off and then
explicitly on again have to do with font-lock-defaults?

Kai

Re: message-mode, compilation, XEmacs 21.4.14

[Chris Green]

Kai Grossjohann <kai@emptydomain.de> writes:

> Chris Green <cmg@dok.org> writes:
>
>> http://thread.gmane.org/gmane.emacs.gnus.general/53254 describes what
>> I'm seeing but the hook solution doesn't help me out here b/c the
>> font-lock-defaults are nil I believe.
>
> Hm?  What does the solution of explicitly turn font-lock off and then
> explicitly on again have to do with font-lock-defaults?

My diagnosis of what was going on w/ font-lock-defaults was completely
off and that thread was as close to describing the problem I'm having
in the archives.

I just now realized that font-lock looks at the properties of the
major-mode to figure out what set of keywords to grab.  I now see that
the message-font-lock-keywords have a different value before I look
at an article and after so I'm trying to trackdown if the original
value I'm getting is something other than in gnus/lisp/message.el
-- 
Chris Green <cmg@dok.org>
Fame may be fleeting but obscurity is forever.

Re: message-mode, compilation, XEmacs 21.4.14

[Chris Green]

Chris Green <cmg@dok.org> writes:

> I just now realized that font-lock looks at the properties of the
> major-mode to figure out what set of keywords to grab.  I now see that
> the message-font-lock-keywords have a different value before I look
> at an article and after so I'm trying to trackdown if the original
> value I'm getting is something other than in gnus/lisp/message.el

Is there anything in for emacs debugging similar to to the watch
command in gdb?  I'd really like to inspect as soon as
message-font-lock-keywords gets modified since single stepping from
gnus-summary-next-article is getting old.  
-- 
Chris Green <cmg@dok.org>
I've had a perfectly wonderful evening. But this wasn't it.
     -- Groucho Marx

Re: message-mode, compilation, XEmacs 21.4.14

[Lars Magne Ingebrigtsen]

Chris Green <cmg@dok.org> writes:

> Is there anything in for emacs debugging similar to to the watch
> command in gdb? 

I don't think so.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen