From: Reuben Thomas <rrt@sc3d.org>
To: Subhan Michael Tindall <SubhanT@familycareinc.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Why don't datetrees use timestamps?
Date: Mon, 16 Mar 2015 21:56:08 +0000 [thread overview]
Message-ID: <CAOnWdogD77AK0iV9q8S8Kz4EYm69CyX5zR=mre3-+cFP5hw6QQ@mail.gmail.com> (raw)
In-Reply-To: <0947dbf0de284ed3b162708f1105b8c5@fcmailsvr2.familycareinc.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On 16 March 2015 at 16:52, Subhan Michael Tindall <SubhanT@familycareinc.org
> wrote:
> You can use a custom capture template and have timestamps of various
> sorts inserted.
>
> For example, I have one datetree I use that inserts a date/time stamp
> using %T (%t gives only date, not time)
>
> See the documentation for capture (hit C-c C C to get into the customize
> interface then scroll down)
>
My question was about the datetree entry headings of the form "2015-03-16
Monday". These aren't controlled by the template. I was interested to know
why these headings look very much like timestamps (and effectively are
timestamps, though at the top level they mention just a year and at the
second level just a year and a month), but aren't actual timestamps.
Eric Fraga said "I don't think it would make sense for the headlines in the
date-tree to have time stamps"; but my question is not why they don't have
time stamps, but why they ARE not time stamps (purely in the formal sense:
the information they contain is already effectively a time stamp, as far as
I can see).
I was hoping to discover the rationale for the design from a developer :)
[-- Attachment #2: Type: text/html, Size: 2214 bytes --]
next prev parent reply other threads:[~2015-03-16 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 17:35 Why don't datetrees use timestamps? Reuben Thomas
2015-03-16 9:21 ` Eric S Fraga
2015-03-16 16:52 ` Subhan Michael Tindall
2015-03-16 21:56 ` Reuben Thomas [this message]
2015-03-17 0:47 ` Nick Dokos
2015-03-18 16:21 ` joakim
2015-03-16 21:58 ` Reuben Thomas
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='CAOnWdogD77AK0iV9q8S8Kz4EYm69CyX5zR=mre3-+cFP5hw6QQ@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=SubhanT@familycareinc.org \
--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).