From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: Leo Gaspard <orgmode@leo.gaspard.io>, emacs-orgmode@gnu.org
Subject: Re: “Fuzzy” times (“evening”, “morning”, “night”…)
Date: Sun, 09 Dec 2018 20:42:05 +0100 [thread overview]
Message-ID: <871s6q8p2q.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <875zw3j4g8.fsf@llwynog.ekleog.org>
Hi Leo,
Leo Gaspard <orgmode@leo.gaspard.io> writes:
> In the process of migrating all my self-organization to org-mode, I
> noticed there is something that cannot currently be encoded in
> timestamps: fuzzy times, where an appointment is made for “Dec 4, Tue,
> evening” but with the hours not yet fixed.
> ...
> To be perfectly honest, my ulterior motive here is to auto-generate
> tasks “Decide of an exact time for [task]” a few days before the
> timestamp. However, I haven't investigated yet whether that'd actually
> be doable and I'm still pretty new to the lisp/emacs/org-mode
> ecosystems, so this may be completely impossible.
>
> What do you think about this idea? Is there a better way to do what I'm
> trying to do with current tools?
What about just adding a tag (:evening:, :morning:, etc.) to represent a
fuzzy time, with a plain date stamp, like <2018-12-04>?
That would allow you to easily create a custom agenda view containing
just entries with fuzzy times (if they have a timestamp with just a
date, you can even filter for those that are coming up in the next
couple of days). Then when it's convenient, you can look at this agenda
view and schedule things that are still fuzzy more precisely.
Hope that helps!
--
Best,
Richard
next prev parent reply other threads:[~2018-12-09 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 17:47 “Fuzzy” times (“evening”, “morning”, “night”…) Leo Gaspard
2018-12-08 18:19 ` Ken Mankoff
2018-12-09 17:00 ` Leo Gaspard
2018-12-09 19:42 ` Richard Lawrence [this message]
2018-12-10 7:55 ` Leo Gaspard
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=871s6q8p2q.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@leo.gaspard.io \
/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).