From: Lars Magne Ingebrigtsen <larsi@gnus.org>
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: Thu, 14 Jul 2011 15:49:41 +0200 [thread overview]
Message-ID: <m3tyap6kga.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <0AEEE18115BA49E58E42C1604867D444@us.oracle.com> (Drew Adams's message of "Fri, 27 Aug 2010 21:06:09 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> 1. For one thing, the Emacs manual deals with it only using a `setq'
> example:
>
> (setq font-lock-maximum-decoration
> '((c-mode . 1) (c++-mode . 1)))
>
> We should tell users how they can use Customize for customizing it.
> (No, it is not obvious how to do that.) We should not be privileging
> Lisp code in .emacs this way - especially fairly complex Lisp code.
For examples of complex variables like this, I find Lisp code a lot
clearer than convoluted Customize settings. So this is not a bug, in my
opinion.
> 2. The doc string and the Customize help for it (same thing) do not help
> much either. In particular, they are missing the info that if you add
> an entry for one or more modes, then you will likely want to also add
> a catch-all entry for all other modes.
The doc string seems to have been fixed in this regard, with a pretty
clear example.
> 3. Also, to understand what the choice of `level' means here, users need
> to know about fontification levels. At least a minimum of info about
> that needs to be presented in the Customize (= doc string) help.
I've now mentioned that higher levels mean more fontification.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-14 13:49 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
2011-07-14 13:49 ` Lars Magne Ingebrigtsen [this message]
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
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=m3tyap6kga.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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 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).