From: Bastien <bzg@altern.org>
To: Rene <jlr_0@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-capture vs. org-agenda-capture
Date: Thu, 13 Dec 2012 00:24:10 +0100 [thread overview]
Message-ID: <871ueu7t2d.fsf@bzg.ath.cx> (raw)
In-Reply-To: <loom.20121212T215736-339@post.gmane.org> (Rene's message of "Wed, 12 Dec 2012 21:24:36 +0000 (UTC)")
Dear Rene,
Rene <jlr_0@yahoo.com> writes:
> As a matter of fact, when called from the agenda `%U' doesn't expand as the
> current timestamp but rather provides the date of the line your point is on.
Depends. From the agenda, you can use either org-capture directly, or
org-agenda-capture. org-capture will convert %U using current time, not
the time of the agenda line -- unless `org-capture-use-agenda-date' is t.
> Wouldn't it be more convenient to get the current timestamp anyway?
If you want the date the cursor is on, I think 00:00 as a default time
makes sense, mixing the current time and the date line would be confusing
IMHO.
> Suppose you would like to create a new appointment then
> 1. you view your agenda to see whether you're free on a particular date
> 2. you place the cursor on that date line
> 3. you invoke org-agenda-capture (hit `k' key) from there
>
> then a template such as this one
>
> ("a" "Appointment" entry (file+headline "~/gtd.org" "Inbox")
> "* APPT %?\n %^T\n Added: %U")
>
> would expand as
>
> * APPT Dentist
> <2012-12-25 Tue 18:00-19:00>
> Added: [2012-12-12 Wed 22:13]
>
> which makes sense; instead of
>
> * APPT Dentist
> <2012-12-25 Tue 18:00-19:00>
> Added: [2012-12-25 Wed 00:00]
>
> as it is today.
I guess M-x org-capture is enough here.
Best,
--
Bastien
next prev parent reply other threads:[~2012-12-12 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 15:23 org-capture vs. org-agenda-capture Rene
2012-12-12 14:40 ` Bastien
2012-12-12 21:24 ` Rene
2012-12-12 23:24 ` Bastien [this message]
2012-12-13 13:13 ` Rene
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=871ueu7t2d.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jlr_0@yahoo.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).