emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Gaspard <orgmode@leo.gaspard.io>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: “Fuzzy” times (“evening”, “morning”, “night”…)
Date: Mon, 10 Dec 2018 02:00:22 +0900	[thread overview]
Message-ID: <87wooihbyx.fsf@llwynog.ekleog.org> (raw)
In-Reply-To: <87bm5vkhk5.fsf@geus3064linuxwsm.geus.dk>

Ken Mankoff <mankoff@gmail.com> writes:
> On 2018-12-08 at 09:47 -0800, Leo Gaspard <orgmode@leo.gaspard.io> wrote:
>> 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)
>> [...]
>> What do you think about this idea? Is there a better way to do what
>> I'm trying to do with current tools?
>
>
> I think this would be a neat feature. But as a first pass which can work immediately, what about using one of the multiple text expansion packages that are Org-agnostic to achieve this: Yasnippets or abbrev mode, for example?
>
> This doesn't maintain the "semantics (time still fuzzy)", but does let you define and enter time ranges in a simpler way.

Hmm… I guess some abbreviation or command could add the fuzzy time and
add a comment to indicate that the time is fuzzy should work as a
temporary workaround indeed, thank you for the idea :)

  reply	other threads:[~2018-12-09 17:00 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 [this message]
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

  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=87wooihbyx.fsf@llwynog.ekleog.org \
    --to=orgmode@leo.gaspard.io \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \
    /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).