From: Samuel Wales <samologist@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Where should I put the timestamp?
Date: Mon, 8 Dec 2014 01:12:07 -0700 [thread overview]
Message-ID: <CAJcAo8vezhPq6MkUrVW5Y_WL=z6N1VA9M2sN1z=4+i6Lfh1nxw@mail.gmail.com> (raw)
In-Reply-To: <871tob9ls3.fsf@amu.edu.pl>
from the user perspective, fwiw, in case it helps, i rely on headlines
like this. they are far better for me than date trees, because you
can sort, show them all at a glance, binary search, less chance of
corruption, no extra hierarchy, etc. they work great in my usage.
===
***** CONVERSATION [2014-12-07 Sun 22:23] called again
they never picked up though.
===
if org ever changes to not allow those, i will stick with the old org
version or carry along a patch in git. :]
On 12/7/14, Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> Hi there,
>
> I vaguely remember someone saying here on the list that putting
> timestamps in the headline is deprecated. However, I found this in the
> manual:
>
> "A timestamp can appear anywhere in the headline or body of an Org tree
> entry. Its presence causes entries to be shown on specific dates in the
> agenda [...]"
>
> Which is wrong: my memory or the manual?
>
> TIA,
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Faculty of Mathematics and Computer Science
> Adam Mickiewicz University
>
>
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: free Karina Hansen NOW.
prev parent reply other threads:[~2014-12-08 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 21:45 Where should I put the timestamp? Marcin Borkowski
2014-12-08 3:54 ` Eric Abrahamsen
2014-12-08 8:12 ` Samuel Wales [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='CAJcAo8vezhPq6MkUrVW5Y_WL=z6N1VA9M2sN1z=4+i6Lfh1nxw@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).