emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Suggestion: rename Org Font Lock customization group
Date: Sun, 28 Mar 2010 14:04:16 -0400	[thread overview]
Message-ID: <871vf4pbkv.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <87mxxsfkpx.fsf@columbia.edu> (Xiao-Yong Jin's message of "Sun, 28 Mar 2010 12:56:58 -0400")

Xiao-Yong Jin <xj2106@columbia.edu> writes:

> 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:
>

Hi Xiao-Yong,

I understand that we may not want to change something that's been this
way in org-mode for ages, but I don't think I understood your arguments:

> I wouldn't invent some new terminology apart from emacs'
> own. 

"Appearance" is not new terminology, it is a very widely-understood
word.

I'm not suggesting that org refer to font lock using a different term;
what I'm suggesting is that that customization group is for changing
Org's *appearance*; in fact, that will often concern internal emacs
implementation machinery known as font-lock, but who needs to know
that?[1]

Also, in the Font Lock customization group, users confront the Emacs
term "Faces", which is a much more important term for a new user to
understand than "Font Lock".

> But I agree that "font lock" is not friendly to new
> users.

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...)

Dan

Footnotes:

[1] I know emacs talks about "buffers", which is only really likely to
make sense initially to the sort of people who know what malloc is, but
I contend that while "buffer" is a towering peak in the linguistic
landscape of emacs, "font-lock" is an obscure and ignorable hillock.



>  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!

  reply	other threads:[~2010-03-28 18:04 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 [this message]
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vf4pbkv.fsf@stats.ox.ac.uk \
    --to=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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).