From: Richard Riley <rileyrg@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Feature-request & documentation request for org-datetree
Date: Wed, 01 Sep 2010 14:56:14 +0200 [thread overview]
Message-ID: <i5lihf$rqk$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTi=ZEqW87yiKApZSyz7O2A2HPtnq2pg-9xhzB33B@mail.gmail.com
"Tim O'Callaghan" <tim.ocallaghan@gmail.com> writes:
> Hi,
>
> I've been poking about trying to understand org-date tree, as It is
> essentially an undocumented feature at the moment. am i right in my
> understanding that it is only meant as a refile-target structure?
>
> The feature request is to allow the use of ISO week numbers to
> structure the year rather than Months.
>
> so a structure something like:
> * 2010
> *** 2010-W35
> ***** 2010-08-30 Monday
> ***** 2010-08-31 Tuesday
> ***** 2010-09-01 Wednesday
> ***** 2010-09-02 Thursday
> ***** 2010-08-03 Friday
> ***** 2010-08-04 Saturday
> ***** 2010-08-05 Sunday
>
> The week heading is based on the ISO representation,
> (http://www.iso.org/iso/date_and_time_format) though i guess some
> variant on the ISO week heading might look be better.
>
> what other use can it be used for? how are other people using it?
>
For me its one of the best features since I use org as a journal for
pretty much everything. My org-capture-templates entry for my journal
creation (also my org-protocol-default-template-key) is
("j" "Journal" entry
(file+datetree "journal.org")
"* %T %?\n %i\n %a")
So bottom line is, I use it for direct filing and not just a refile
target. A super feature. The %T meaning of course in my agenda I see the
date and time a journal item is added "in place" even if I then
reschedule it and refile it at a later date.
next prev parent reply other threads:[~2010-09-01 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 11:44 Feature-request & documentation request for org-datetree Tim O'Callaghan
2010-09-01 12:56 ` Richard Riley [this message]
2010-09-02 9:40 ` Carsten Dominik
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='i5lihf$rqk$1@dough.gmane.org' \
--to=rileyrg@gmail.com \
--cc=emacs-orgmode@gnu.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).