From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 6935@debbugs.gnu.org
Subject: bug#6935: 24.0.50; doc for `font-lock-maximum-decoration'
Date: Mon, 30 Aug 2010 08:46:57 -0700 [thread overview]
Message-ID: <94F453208A4B4F70B7C5F87CB2BE541C@us.oracle.com> (raw)
In-Reply-To: <jwvk4n8mahe.fsf-monnier+emacs@gnu.org>
> > This customization option lets users easily pick the level
> > they want. Just yesterday I had a user report about this
> > wrt Dired+ (my code had a bug that was preventing such a
> > choice). Users have different needs
> > and preferences, and they do care about them.
>
> 2 reasons:
> - rather than let people work around problems by reducing the
> level,
It's not a question of "working around" anything. It's about providing levels
to give users a choice.
> we should work harder to make sure that the default level is OK
> for everyone.
That's silly. If there is a _default_ level then there are level choices and a
notion of level.
No one disagrees that the default level should provide minimal fontification.
The point is to allow users to move to a higher level if they so wish.
> - "level" is the wrong way to think about this. Instead, we
> should have separate controls for different font-lock features.
Be specific. If you are agreeing that users should have choice and control when
it comes to the degree of font-locking, and you just disagree with the current
"level" mechanism, then propose something specific.
Note that in the case I cited the user had the ability to fine-tune
fontification, for example by customizing individual faces. But he wanted a
coarse-grain control, to change the _level_.
That was so even though he was unaware of the current level mechanism. He
sought a way to affect the level of fontification in one fell swoop. And that's
just what the current level mechanism offers.
If you have a better way to give users that possibility, then please propose it
specifically (on emacs-devel).
I'd certainly agree that the current mechanism does not give users a way to
define the makeup of a given level themselves, and that that is a limitation.
The makeup of each level is hard-coded. I, for one, would welcome a feature
that lets users (easily) define what each level should be.
That would likely mean letting them customize the font-lock keywords for each
level in some way. And currently there is no good way for users to use
Customize to tailor a set of font-lock keywords.
next prev parent reply other threads:[~2010-08-30 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 4:06 bug#6935: 24.0.50; doc for `font-lock-maximum-decoration' Drew Adams
2010-08-28 14:41 ` Stefan Monnier
2010-08-28 19:54 ` Drew Adams
2010-08-30 14:41 ` Stefan Monnier
2010-08-30 15:46 ` Drew Adams [this message]
2010-08-30 22:04 ` Stefan Monnier
2010-08-30 22:56 ` Drew Adams
2010-08-31 10:33 ` Stefan Monnier
2011-07-14 13:49 ` Lars Magne Ingebrigtsen
2011-07-14 16:41 ` Drew Adams
2011-07-22 3:54 ` Chong Yidong
2011-07-31 15:00 ` Lars Magne Ingebrigtsen
2011-07-31 16:31 ` Drew Adams
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=94F453208A4B4F70B7C5F87CB2BE541C@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=6935@debbugs.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.