From: Detlef Steuer <detlef.steuer@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: How to extract TODOs from date-tree
Date: Wed, 29 Oct 2014 16:15:24 +0100 [thread overview]
Message-ID: <20141029161524.2139ba3a@gaia> (raw)
In-Reply-To: 87fve79ie8.fsf@pierrot.dokosmarshall.org
Am Wed, 29 Oct 2014 08:20:47 -0400
schrieb Nick Dokos <ndokos@gmail.com>:
> Detlef Steuer <detlef.steuer@gmx.de> writes:
>
> > Hi Nick!
> >
> >
> >> If there are use cases out there, it might be worth collecting them
> >> and then thinking about how to support them better. If there
> >> aren't, maybe it should be thrown out.
> >>
> >
> >
> > Oh, NO, don´t do that! Datetrees were a major enhancement for my
> > workflow. I use one as a kind of "lab logbook" and time tracker.
> >
> > Fits my use very well and I would miss it a lot!
> >
> > I think datetrees work like intended and stable.
> >
>
> Yes, that was a bit provocative, wasn't it? I don't think there is
> any need to worry.
>
> Could you describe your use case?
Nothing to see here: Just hitting C-c a a i j a few times during a day
and add some notes for today in a diary/logbook. That's it.
I'm quite happy about the status quo.
Detlef
> Maybe it could fill the hole in the
> manual. Also, maybe my impression that it's thinly supported may be
> wrong, but you would know better: is there datetree functionality that
> you find yourself wishing for?
>
next prev parent reply other threads:[~2014-10-29 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 15:53 How to extract TODOs from date-tree Jay Iyer
2014-10-28 16:20 ` Thorsten Jolitz
2014-10-28 16:54 ` Jay Iyer
2014-10-28 17:26 ` Thorsten Jolitz
2014-10-28 17:28 ` Thorsten Jolitz
2014-10-29 2:59 ` Nick Dokos
2014-10-29 8:24 ` Detlef Steuer
2014-10-29 12:20 ` Nick Dokos
2014-10-29 15:15 ` Detlef Steuer [this message]
2014-10-29 12:27 ` Alexander Baier
2014-10-29 15:28 ` Jay Iyer
2014-10-29 19:34 ` Robert Horn
2014-11-02 21:00 ` Alan Schmitt
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=20141029161524.2139ba3a@gaia \
--to=detlef.steuer@gmx.de \
--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).