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 12:56:58 -0400 [thread overview]
Message-ID: <87mxxsfkpx.fsf@columbia.edu> (raw)
In-Reply-To: <87d3yopgna.fsf@stats.ox.ac.uk> (Dan Davison's message of "Sun, 28 Mar 2010 12:14:49 -0400")
On Sun, 28 Mar 2010 12:14:49 -0400, Dan Davison wrote:
> For the sake of non-emacs experts, I think the customization group
> "Org Font Lock" would be better named "Org Appearance". Here's what part of
> the org-customize buffer currently looks like:
I wouldn't invent some new terminology apart from emacs'
own. But I agree that "font lock" is not friendly to new
users. We could mention this in info and tutorial so users
new to emacs can know what they should look for.
> [+]-- Group Org TODO
> [+]-- Group Org Time
> [+]-- Group Org Tags
> [+]-- Group Org Properties
> [+]-- Group Org Agenda
> [+]-- Group Org LaTeX
> [-]-\ Group Org Font Lock
>> [+]-- Group Org Faces
>> |--- Option Org Odd Levels Only
>> |--- Option Org Level Color Stars Only
>> |--- Option Org Hide Leading Stars
>> |--- Option Org Hidden Keywords
>> |--- Option Org Fontify Done Headline
>> |--- Option Org Fontify Emphasized Text
>> |--- Option Org Fontify Whole Heading Line
>> |--- Option Org Highlight Latex Fragments And Specials
>> |--- Option Org Hide Emphasis Markers
>> |--- Option Org Emphasis Regexp Components
>> `--- Option Org Emphasis Alist
> [+]-- Group Org Completion
It looks really nice. Thanks!
--
J c/* __o/*
X <\ * (__
Y */\ <
next prev parent reply other threads:[~2010-03-28 16:57 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 [this message]
2010-03-28 18:04 ` Dan Davison
2010-03-28 18:11 ` Dan Davison
2010-03-28 19:34 ` Xiao-Yong Jin
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=87mxxsfkpx.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.