Subject: bug#32027: AW: bug#32027: 26.1; variable font-lock-major-mode is nil in text-mode

From: Benjamin Orthen <[email-masked]>
Date: Tue, 3 Jul 2018 09:21:55 +0000

Correction: I meant font-lock-major-mode, not global-font-lock-mode.

________________________________
Von: Benjamin Orthen
Gesendet: Dienstag, 3. Juli 2018 11:20:58
An: Eli Zaretskii
Cc: [email-masked]
Betreff: AW: bug#32027: 26.1; variable font-lock-major-mode is nil in text-mode

Thanks for replying so quickly.

> Because Text mode doesn't set up any font-lock related settings, no?

But why does running M-x font-lock-mode twice (disabling and enabling font-lock) in a text buffer set

global-font-lock-mode to text-mode then? I would consider that kind of erratic behavior.

E.g. hi-lock-mode in text-mode requires font-lock-major-mode to be set to text-mode to work.

________________________________
Von: Eli Zaretskii <[email-masked]>
Gesendet: Montag, 2. Juli 2018 17:08:21
An: Benjamin Orthen
Cc: [email-masked]
Betreff: Re: bug#32027: 26.1; variable font-lock-major-mode is nil in text-mode

> From: Benjamin Orthen <[email-masked]>
> Date: Sun, 1 Jul 2018 19:53:14 +0000
>
> Problem:
>
> The variable font-lock-major-mode is nil after opening a text file, even
> when global-font-lock-mode is set to t and font-lock-mode is set to t in buffer.

Because Text mode doesn't set up any font-lock related settings, no?