From: Memnon Anon <email@example.com>
Subject: Re: org-capture in the same file from which it was called under certain heading
Date: Sat, 28 May 2011 12:15:08 +0000 (UTC) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Rainer M Krug <email@example.com> writes:
> Yes - exactly that. Now if this could go into the documentation of
> org-capture, that would be great.
The doc string of `org-capture-templates' concisely says:
| A file can also be given as a variable, function, or Emacs Lisp
So it is documented already.
(Note to self:
"Docstrings deserve closer attention. Do not only skim over them anymore!")
Might be worth a footnote in the manual.
OTOH, this seems to be sort of a corner case;
the manual should not try to encompass everything there is...
prev parent reply other threads:[~2011-05-28 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 10:17 org-capture in the same file from which it was called under certain heading Rainer M Krug
2011-05-28 10:00 ` Memnon Anon
2011-05-28 10:03 ` Rainer M Krug
2011-05-28 11:40 ` Yagnesh Raghava Yakkala
2011-05-28 13:15 ` Memnon Anon
2011-05-28 14:50 ` Bernt Hansen
2011-05-28 12:15 ` Memnon Anon [this message]
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).