emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Beginners guide to Org customization
Date: Thu, 05 Feb 2009 09:21:37 -0500	[thread overview]
Message-ID: <87fxitotfy.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <33DFD2BB-A6FC-43AE-9DE0-5E5DE0802F4A@uva.nl> (Carsten Dominik's message of "Thu\, 5 Feb 2009 12\:54\:40 +0100")

Carsten Dominik <dominik@science.uva.nl> 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_ using
org-mode for awhile.  Maybe the following variables should be introduced
later?

  - org-archive-location

    the default works, and you don't archive anytime soon after starting
    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 nor
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
away.

Maybe we just need to stress that customizations are optional and you
can completely ignore entire sections that don't apply to you (clocking,
exporting, etc.) until you feel you need these additional features.

HTH,
Bernt

  parent reply	other threads:[~2009-02-05 14:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 11:54 Carsten Dominik
2009-02-05 13:25 ` David Lord
2009-02-05 13:52   ` Carsten Dominik
2009-02-05 14:21 ` Bernt Hansen [this message]
2009-02-05 14:34   ` Carsten Dominik
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

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=87fxitotfy.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Beginners guide to Org customization' \
    /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

Code repositories for project(s) associated with this 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).