From: Carsten Dominik <firstname.lastname@example.org>
To: Bernt Hansen <email@example.com>
Cc: emacs-orgmode Mailinglist <firstname.lastname@example.org>
Subject: Re: Beginners guide to Org customization
Date: Thu, 5 Feb 2009 15:34:33 +0100 [thread overview]
Message-ID: <18C7F5EB-B251-4F91-9406-654FBF305D8B@uva.nl> (raw)
Hi Bernt, good suggestions, thanks.
The list I made closely adheres to the most frequently set variables.
But I think you are right, we should be more restrictive here.
I will do what you suggest. I think I will even remove the entire
clock section, for example, and instead add documentation about clock
persistence to the manual (actually, I just did that).
On Feb 5, 2009, at 3:21 PM, Bernt Hansen wrote:
> Carsten Dominik <email@example.com> writes:
>> I have made a structured list of 43 (which one can
>> we remove, please????) Variables that came in as frequently
>> customized variables in the customization survey. It is not
>> exactly the top 43, I have used some additional judgement.
> I think a lot of these variables are things you play with _after_
> org-mode for awhile. Maybe the following variables should be
> - org-archive-location
> the default works, and you don't archive anytime soon after
> to use org-mode.
> - org-startup-folded
> start with #STARTUP first?
> - org-odd-levels-only
> Talk about the conversion functions too (org-convert-to-odd-levels
> and org-convert-to-oddeven-levels.) I switched my files back and
> forth a few times but ended up with oddeven levels due to the depth
> of some of my tasks.
> - org-special-ctrl-a/e
> - org-special-ctrl-k
> I should maybe try these one day :)
> I've used org-mode for a few years now and I don't currently use these
> variables. They're great to have but not essential to getting started.
> The default values for the variables work in most cases. I think the
> ones that should be listed first are the ones you really have to
> customize to get org-mode to work for you. Beginners will not want
> need this amount of detail to be productive with org-mode. Having too
> many variables to set up or play with up front may just scare people
> Maybe we just need to stress that customizations are optional and you
> can completely ignore entire sections that don't apply to you
> exporting, etc.) until you feel you need these additional features.
next prev parent reply other threads:[~2009-02-05 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 11:54 Beginners guide to Org customization Carsten Dominik
2009-02-05 13:25 ` David Lord
2009-02-05 13:52 ` Carsten Dominik
2009-02-05 14:21 ` Bernt Hansen
2009-02-05 14:34 ` Carsten Dominik [this message]
2009-02-05 17:29 ` Carsten Dominik
2009-02-05 18:01 ` Bernt Hansen
2009-02-05 21:40 ` Carsten Dominik
2009-02-05 18:13 ` Graham Smith
2009-02-06 11:09 Rustom Mody
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).