emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Inactive time stamps along with CLOCK: entries?
Date: Wed, 09 Nov 2011 20:27:33 +0100	[thread overview]
Message-ID: <80fwhxjdui.fsf@somewhere.org> (raw)
In-Reply-To: 87lirpdxyo.fsf@norang.ca

Hi Bernt and Tommy,

Bernt Hansen wrote:
> Tommy Kelly <tommy.kelly-ABZRMiVa18FBDgjK7y7TUQ@public.gmane.org> writes:
>
>> Question for Bernt, but maybe more widely useful.
>>
>> Bernt, in some of your org-capture-templates, you often include a %U
>> timestamp as well as clocking in the item in question. for example:
>>
>> ("j" "Journal" entry (file+datetree "~/git/org/diary.org")
>>                "* %?\n%U\n  %i" :clock-in t :clock-resume t)
>>
>> Why do you do that extra \n%U? Since the timestamp is going to be
>> identical to the first entry in the CLOCK: line, and since you can
>> have/not-have clocking items show up in the agenda, why have both the
>> :CLOCK line and the timestamp? What else do you get from having a
>> timestamp that you don't get from the CLOCK: line alone?
>
> The reason I have both is I create capture tasks and notes _fast_ and
> remove empty clock lines - so there is no clock line or clock drawer
> when I'm done in that that.
>
> The %U is to record when I created the task/note.

Could sorting of entries be another reason: possible with inactive timestamp,
not with first clock line?

Best regards,
  Seb

-- 
Sebastien Vauban

      reply	other threads:[~2011-11-09 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 13:23 Inactive time stamps along with CLOCK: entries? Tommy Kelly
2011-11-09 17:09 ` Bernt Hansen
2011-11-09 19:27   ` Sebastien Vauban [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=80fwhxjdui.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /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).