emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Beginners guide to Org customization
Date: Thu, 5 Feb 2009 22:40:07 +0100	[thread overview]
Message-ID: <58D3255C-431E-4F85-B6C3-850213F16063@uva.nl> (raw)
In-Reply-To: <87hc38lq5e.fsf@gollum.intra.norang.ca>

On Feb 5, 2009, at 7:01 PM, Bernt Hansen wrote:

> Carsten,
> That looks really good! (except for the FIXME at the bottom ;) )
> I really like this version :)
> I haven't verified that the setup steps you described actually work.
> Somebody(tm) should probably do that with a minimal emacs setup.
> I also haven't verified all the links referenced in the document go to
> appropriate places.
> Hmmm my setup doesn't have (org-remember-insinuate) (well it does
> now!) -- I wonder what breaks if that is missing.

org-remember-insinuate is simply a shortcut for the
old setup where you had to add functions to hooks yourself.
The definition of it is:

(defun org-remember-insinuate ()
   "Setup remember.el for use with Org-mode."
   (setq remember-annotation-functions '(org-remember-annotation))
   (setq remember-handler-functions '(org-remember-handler))
   (add-hook 'remember-mode-hook 'org-remember-apply-template))

It actually does one more thing:  If remember.el is not
found, it defines a miniature, just functional version of it.

- Carsten

> -Bernt
> Carsten Dominik <dominik@science.uva.nl> writes:
>> I have my home^h^h^h^h trainwork up as a new
>> attempt for the "Beginners Guide".
>> A lot more appropriate now, I think.  Bernt?
>> - Carsten
>> http://orgmode.org/worg/org-customization-guide.php
>> On Feb 5, 2009, at 3:21 PM, Bernt Hansen wrote:
>>> 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

  reply	other threads:[~2009-02-05 21:40 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
2009-02-05 17:29   ` Carsten Dominik
2009-02-05 18:01     ` Bernt Hansen
2009-02-05 21:40       ` Carsten Dominik [this message]
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:

  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=58D3255C-431E-4F85-B6C3-850213F16063@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \


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