all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Gaspard <orgmode@leo.gaspard.io>
To: emacs-orgmode@gnu.org
Subject: “Fuzzy” times (“evening”, “morning”, “night”…)
Date: Sun, 09 Dec 2018 02:47:35 +0900	[thread overview]
Message-ID: <875zw3j4g8.fsf@llwynog.ekleog.org> (raw)

Hello,

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.

Currently my way of handling this has been to mark the tasks with time
spans approx. correct and add a comment to fix them.

However, I think it may be a good idea to allow eg. this kind of
timestamps:
        <2018-02-04 Tue evening>
That would be handled as though it was eg. <2018-02-04 Tue 18:00-22:00>
(which would be configurable), so that it would be both semantically
correct (the time is still fuzzy) and correctly displayed (eg. on an
agenda)

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?

Cheers,
Leo

             reply	other threads:[~2018-12-08 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 17:47 Leo Gaspard [this message]
2018-12-08 18:19 ` “Fuzzy” times (“evening”, “morning”, “night”…) Ken Mankoff
2018-12-09 17:00   ` Leo Gaspard
2018-12-09 19:42 ` Richard Lawrence
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875zw3j4g8.fsf@llwynog.ekleog.org \
    --to=orgmode@leo.gaspard.io \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.