[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…)
From: |
Leo Gaspard |
Subject: |
Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…) |
Date: |
Mon, 10 Dec 2018 02:00:22 +0900 |
Ken Mankoff <address@hidden> writes:
> On 2018-12-08 at 09:47 -0800, Leo Gaspard <address@hidden> 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 :)
- [O] “Fuzzy” times (“evening”, “morning”, “night”…), Leo Gaspard, 2018/12/08
- Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…), Ken Mankoff, 2018/12/08
- Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…),
Leo Gaspard <=
- Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…), Richard Lawrence, 2018/12/09