From: Jari Aalto <jari.aalto@tamk.fi>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Stefan Monnier' <monnier@IRO.UMontreal.CA>,
2459@emacsbugs.donarmstrong.com,
'Jari Aalto' <jari.aalto@cante.net>
Subject: bug#2459: 22.2.1: global-font-lock-mode does not turn off colors:ido.el, minibuffer prompt
Date: Thu, 26 Feb 2009 16:16:14 +0200 [thread overview]
Message-ID: <871vtlthap.fsf@jondo.cante.net> (raw)
In-Reply-To: <002b01c9976d$dbf8e0c0$c2b22382@us.oracle.com> (Drew Adams's message of "Wed, 25 Feb 2009 09:24:04 -0800")
> "Drew Adams" <drew.adams@oracle.com> writes:
> The use case seems to be only to turn off *all* highlighting. We should find a
> good way to handle that particular use case. Equating all highlighting to
> font-lock highlighting, just to respond to this use case, would be using a
> sledge hammer to kill a fly - a step backward.
It's natural that people have years trained themselves to use:
M-x global-font-lock-mode
to turn on and off colors. Globally. From user's M-x perspective, the
font-lock is synonym for controlling the "colors", whether in technical
level the implementation and use of font-lock may differ.
> Richard M Stallman <rms@gnu.org> writes:
> This sort of problem is easy to fix; we already have a mechanism for
> it. The mode should set `font-lock-face' properties instead of `face'
> properties. That will make the right thing happen.
That'd be welcomed
Thanks,
Jari
next prev parent reply other threads:[~2009-02-26 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 11:54 bug#2459: 22.2.1: global-font-lock-mode does not turn off colors: ido.el, minibuffer prompt Jari Aalto
2009-02-24 18:17 ` Glenn Morris
2009-02-24 18:30 ` Processed: " Emacs bug Tracking System
2009-02-24 19:31 ` Jari Aalto
2009-02-24 19:56 ` Juri Linkov
2009-02-25 15:53 ` Richard M Stallman
2009-02-25 16:49 ` Stefan Monnier
2009-02-25 17:24 ` bug#2459: 22.2.1: global-font-lock-mode does not turn off colors:ido.el, " Drew Adams
2009-02-26 14:16 ` Jari Aalto [this message]
2009-02-26 19:25 ` Richard M Stallman
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=871vtlthap.fsf@jondo.cante.net \
--to=jari.aalto@tamk.fi \
--cc=2459@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
--cc=jari.aalto@cante.net \
--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.