From: Xiao-Yong Jin <xj2106@columbia.edu>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Suggestion: rename Org Font Lock customization group
Date: Sun, 28 Mar 2010 15:34:56 -0400 [thread overview]
Message-ID: <87iq8gfden.fsf@columbia.edu> (raw)
In-Reply-To: <871vf4pbkv.fsf@stats.ox.ac.uk> (Dan Davison's message of "Sun, 28 Mar 2010 14:04:16 -0400")
On Sun, 28 Mar 2010 14:04:16 -0400, Dan Davison wrote:
> Right, when being friendly to new users is the purpose of customize.
> A further argument that "Font Lock" is a misnomer is that "Org Odd
> Levels Only" is not related to font lock. It could be put in Structure,
> but I think the decision to put it in the same group as all the other
> variables related to appearance made sense.
> And I think there may be other examples of things that are more
> helpfully described as "Appearance" than "Font Lock". For example, some
> of the options in the "Org Startup" group might benefit from also having
> an entry in an appearance group, e.g. org-hide-block-startup. Or perhaps
> we could have an option to control whether links to images are replaced
> in the buffer by the image? (a topic for a different thread...)
Hi Dan,
I previously thought it might confuse new users if we use
different term specifically for org-mode. But now I
completely agree with you. "Appearance" is indeed a much
better word for this customize group.
--
J c/* __o/*
X <\ * (__
Y */\ <
next prev parent reply other threads:[~2010-03-28 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 16:14 Suggestion: rename Org Font Lock customization group Dan Davison
2010-03-28 16:56 ` Xiao-Yong Jin
2010-03-28 18:04 ` Dan Davison
2010-03-28 18:11 ` Dan Davison
2010-03-28 19:34 ` Xiao-Yong Jin [this message]
2010-03-28 21:53 ` Carsten Dominik
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=87iq8gfden.fsf@columbia.edu \
--to=xj2106@columbia.edu \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@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.
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.