From: Michal Nazarewicz <mina86@mina86.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] font-core: add font-lock-{enable, disable}-global-for functions
Date: Sun, 04 Jan 2015 15:43:59 +0100 [thread overview]
Message-ID: <xa1t61cm38sw.fsf@mina86.com> (raw)
In-Reply-To: <54A94BA7.8000705@yandex.ru>
On Sun, Jan 04 2015, Dmitry Gutov <dgutov@yandex.ru> wrote:
> On 01/04/2015 04:39 PM, Stefan Monnier wrote:
>>>> (add-hook 'compilation-mode-hook (lambda () (font-lock-mode -1)))
>>> So what is font-lock-global-modes for anyway?
>>
>> I don't know.
>
> For centralized user customization, I believe.
>
> It's a nice pattern: you see all the major modes font-lock-mode won't be
> enabled in. I've copied it in company-mode when users asked for this
> capability.
It doesn't work with derived modes though, does it?
Also, if that's a pattern that's going to be repeated, should there be
some centralised code for handling it?
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
next prev parent reply other threads:[~2015-01-04 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 15:51 [PATCH] font-core: add font-lock-{enable, disable}-global-for functions Michal Nazarewicz
2015-01-04 2:27 ` Stefan Monnier
2015-01-04 3:21 ` Michal Nazarewicz
2015-01-04 4:30 ` Stefan Monnier
2015-01-04 6:07 ` Michal Nazarewicz
2015-01-04 13:39 ` Stefan Monnier
2015-01-04 14:18 ` Dmitry Gutov
2015-01-04 14:43 ` Michal Nazarewicz [this message]
2015-01-04 14:56 ` Dmitry Gutov
2015-01-04 19:42 ` Stefan Monnier
2015-01-04 22:07 ` Dmitry Gutov
2015-01-04 23:44 ` Stefan Monnier
2015-01-05 0:02 ` Dmitry Gutov
2015-01-05 0:08 ` Dmitry Gutov
2015-01-05 1:49 ` Stefan Monnier
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=xa1t61cm38sw.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.