From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: help in same window + colorful help + Blümchen
Date: Wed, 08 Jul 2015 13:20:04 -0400 [thread overview]
Message-ID: <mnjm1f$it2$1@dont-email.me> (raw)
In-Reply-To: mailman.6563.1436375087.904.help-gnu-emacs@gnu.org
Drew Adams <drew.adams@oracle.com> writes:
>> It's not a case of "there could be", there already is:
>>
>> You can customize the variable font-lock-maximum-decoration to
>> alter the amount of fontification applied by Font Lock mode, for
>> major modes that support this feature. The value should be a number
>> (with 1 representing a minimal amount of fontification; some modes
>> support levels as high as 3); or t, meaning “as high as possible”
>> (the default).
>
> Yes. Unfortunately, there are *very few* places where Emacs code
> provides more than one fontification level. And the Emacs maintainer
> is not particularly fond of the existence and use of levels. (He will
> perhaps chime in, especially if I misrepresented his position on this.)
I don't find that too surprising, I can't think of anything in Emacs
that identifies too many things. I'd guess the trade off would be
speed vs. identification and font-lock speed hasn't been an issue for
me for ages.
> (FWIW, Dired+ provides a second fontification level for Dired.)
My point was that the levels are already there,
whether they are useful is another matter.
--
Dan Espen
next prev parent reply other threads:[~2015-07-08 17:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 22:47 help in same window + colorful help + Blümchen Emanuel Berg
2015-07-07 23:46 ` Ian Zimmerman
2015-07-08 7:03 ` tomas
2015-07-08 10:41 ` Emanuel Berg
2015-07-08 11:13 ` tomas
2015-07-08 11:28 ` Emanuel Berg
2015-07-08 12:13 ` tomas
2015-07-08 23:04 ` Emanuel Berg
2015-07-08 12:28 ` Michael Heerdegen
2015-07-08 12:56 ` tomas
2015-07-08 22:48 ` Emanuel Berg
2015-07-09 6:27 ` tomas
2015-07-09 22:17 ` Emanuel Berg
2015-07-10 3:55 ` tomas
2015-07-10 16:08 ` Emanuel Berg
2015-07-10 17:00 ` Ian Zimmerman
[not found] ` <mailman.6682.1436547616.904.help-gnu-emacs@gnu.org>
2015-07-10 20:04 ` Dan Espen
2015-07-11 19:01 ` Emanuel Berg
2015-07-08 17:17 ` Drew Adams
2015-07-08 22:56 ` Emanuel Berg
2015-07-08 22:43 ` Emanuel Berg
[not found] ` <mailman.6546.1436358510.904.help-gnu-emacs@gnu.org>
2015-07-08 13:31 ` Dan Espen
2015-07-08 17:04 ` Drew Adams
[not found] ` <mailman.6563.1436375087.904.help-gnu-emacs@gnu.org>
2015-07-08 17:20 ` Dan Espen [this message]
2015-07-08 14:34 ` Raffaele Ricciardi
-- strict thread matches above, loose matches on Subject: below --
2015-07-08 7:09 martin rudalics
2015-07-08 9:55 ` Emanuel Berg
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='mnjm1f$it2$1@dont-email.me' \
--to=despen@verizon.net \
--cc=help-gnu-emacs@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.
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).