unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Michal Nazarewicz <mina86@mina86.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] font-core: add font-lock-{enable, disable}-global-for functions
Date: Sun, 04 Jan 2015 20:49:16 -0500	[thread overview]
Message-ID: <jwvfvbq9f3y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <54A9D487.6070109@yandex.ru> (Dmitry Gutov's message of "Mon, 05 Jan 2015 03:02:15 +0300")

> My version is more complicated: in some cases we might want derived modes to
> be affected, in others not.  A graphical interface for picking the modes and
> modifiers might turn out to be more confusing than editing the Lisp form.

I don't think we want that level of control in this kind of simple UI,
because it complexifies it for a very rare case anyway: it's not worth
the trouble.

>> That's no worse than the current font-lock-global-modes.
> It makes no pretence of solving that problem, though.  Often that's
> better than solving a problem halfway (no misconceptions for the
> user).

I didn't mean to claim that it solves this problem.  I only meant it as
a way to add elements to major-mode modes hooks, but seen from the point
of the view of "the element versus all the modes on which it can apply"
(and then remove the things you added this way).

It shouldn't try to recognize elements added via some other way
than Custom.


        Stefan



      parent reply	other threads:[~2015-01-05  1:49 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
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 [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvfvbq9f3y.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=mina86@mina86.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).