From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 6935@debbugs.gnu.org
Subject: bug#6935: 24.0.50; doc for `font-lock-maximum-decoration'
Date: Tue, 31 Aug 2010 12:33:00 +0200 [thread overview]
Message-ID: <jwvaao3gjoy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <25DFEB9F124E49EA82BB01E0A16107C0@us.oracle.com> (Drew Adams's message of "Mon, 30 Aug 2010 15:56:07 -0700")
> But you apparently disagree with yourself in that case, since you
> argue both for letting them move to a lower level and not letting them
> change level at all (no levels).
Not I do not argue for them to be able to lower the level. That's just
the functionality currently provided, and which I dislike.
> Be specific. Which different font-lock features for which mode?
> You're just hand-waving, saying that we could split fontification into
> a set of "features" rather than a set of levels. Sounds fine at that
> level of abstraction (simply replacing numeric "levels" by boolean
> "features"), but the proof is in the pudding.
I see no need for being more specific: whenever a particular need
arises, we add a corresponding config.
> Sure, there are lots of such considerations. I don't oppose
> a superior design that gives users _more_ control over what gets
> highlighted, where, how much, etc.
I'm glad we agree.
> But where's the beef? Where's the specific proposal? Don't just say
> we should drop the user control we do offer without offering something
> better.
Strawman.
Stefan
next prev parent reply other threads:[~2010-08-31 10:33 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
2010-08-30 22:04 ` Stefan Monnier
2010-08-30 22:56 ` Drew Adams
2010-08-31 10:33 ` Stefan Monnier [this message]
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=jwvaao3gjoy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6935@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.