From: Benjamin Orthen <benjamin.orthen@tum.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "32027@debbugs.gnu.org" <32027@debbugs.gnu.org>
Subject: bug#32027: AW: bug#32027: 26.1; variable font-lock-major-mode is nil in text-mode
Date: Tue, 3 Jul 2018 09:20:58 +0000 [thread overview]
Message-ID: <27190ac902c64a8e94effc9ba6244a30@tum.de> (raw)
In-Reply-To: <83zhz9k74q.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
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 <eliz@gnu.org>
Gesendet: Montag, 2. Juli 2018 17:08:21
An: Benjamin Orthen
Cc: 32027@debbugs.gnu.org
Betreff: Re: bug#32027: 26.1; variable font-lock-major-mode is nil in text-mode
> From: Benjamin Orthen <benjamin.orthen@tum.de>
> 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?
[-- Attachment #2: Type: text/html, Size: 2122 bytes --]
next prev parent reply other threads:[~2018-07-03 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 19:53 bug#32027: 26.1; variable font-lock-major-mode is nil in text-mode Benjamin Orthen
2018-07-02 15:08 ` Eli Zaretskii
2018-07-03 9:20 ` Benjamin Orthen [this message]
2018-07-03 9:21 ` bug#32027: AW: " Benjamin Orthen
2019-10-30 18:51 ` Lars Ingebrigtsen
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=27190ac902c64a8e94effc9ba6244a30@tum.de \
--to=benjamin.orthen@tum.de \
--cc=32027@debbugs.gnu.org \
--cc=eliz@gnu.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.