emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: Memnon Anon <gegendosenfleisch@googlemail.com>, emacs-orgmode@gnu.org
Subject: Re: Re: New to org-capture (and org-remember)
Date: Fri, 2 Jul 2010 10:57:13 +0200	[thread overview]
Message-ID: <06A5639E-6B39-45CD-88D4-0D6E0A36B78A@gmail.com> (raw)
In-Reply-To: <8331.1278060218@maps>

Hi Stephen,

On Jul 2, 2010, at 10:43 AM, Stephen Eglen wrote:

> Memnon Anon <gegendosenfleisch@googlemail.com> wrote:
>
>> Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk> writes:
>>
>>> I'd like to try out org-capture.
>>>
>>> I've never used org-remember before so I have no templates to  
>>> convert.
>>> Do I make the new ones in pretty much the same way as the manual
>>> describes for org-remember?
>>>
>>> Or should I be patient, and wait for org-capture to stabilise?
>>
>> Hi,
>>
>> to quote the fine manual:
>>
>> ,----[ (info "(org)Capture templates") ]
>> | You can use templates to arrange for different types of capture  
>> items,
>> | and for different target locations.  The easiest way to set up such
>> | templates is through the customize interface.
>> |
>> | `C-c c C'
>> |      Customize the variable `org-capture-templates'.
>> `----
>>
>> Is your documentation uptodate?
>>
>> You should find all the information in "9.1 Capture" and its
>> subnodes to get you started.
>>
>> Argh, org-capture.el is not part of the current stable release.
>> So, if you want to try, you need the development version, either
>> with git or download org-latest (link is on orgmode.org).
>>
>> If you still encounter any problems, please describe them so the
>> documentation can be improved :).
>
> Thanks for this.  I have read the nice docs (and found some small  
> typos
> - will send a patch).

Proofreading that section carefully would be much appreciated.
Also better wording etc.  I am known as the worst typist in the world,
and I know that my English is reasonably good but not nearly perfect.

>
> One thing immediately struck me: sec 9.1.1. mentions setting:
> org-default-notes-file
> but I couldn't see that mentioned in the rest of the chapter.  Its
> docstring would indicate its needed by remember.el, so perhaps there  
> is
> no need any more to set org-default-notes-file?

I have just updated this docstring, thanks for noticing this.

This variable is not necessary, but it is used if you are too
lazy to give a target file in the template definition.

- Carsten

      reply	other threads:[~2010-07-02  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 15:28 New to org-capture (and org-remember) Stephen Eglen
2010-07-01 15:31 ` Carsten Dominik
2010-07-01 15:50 ` Memnon Anon
2010-07-02  8:43   ` Stephen Eglen
2010-07-02  8:57     ` Carsten Dominik [this message]

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=06A5639E-6B39-45CD-88D4-0D6E0A36B78A@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=S.J.Eglen@damtp.cam.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=gegendosenfleisch@googlemail.com \
    /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).