On 2020-05-02, at 10:12, to...@tuxteam.de wrote:
> On Sat, May 02, 2020 at 09:37:40AM +0200, Marcin Borkowski wrote:
>>
>> On 2020-04-30, at 07:02, Kyle Meyer wrote:
>>
>> > And note that a utility like datefudge or libfaketime is useful for
>> > testing these sorts of things out. For
On Sat, May 02, 2020 at 09:37:40AM +0200, Marcin Borkowski wrote:
>
> On 2020-04-30, at 07:02, Kyle Meyer wrote:
>
> > And note that a utility like datefudge or libfaketime is useful for
> > testing these sorts of things out. For example:
> >
> > $ datefudge "2020-02-18" emacs [...]
>
>
On 2020-04-30, at 07:02, Kyle Meyer wrote:
> And note that a utility like datefudge or libfaketime is useful for
> testing these sorts of things out. For example:
>
> $ datefudge "2020-02-18" emacs [...]
Shameless plug: I wrote about this use-case of datefudge sime time ago:
Vladimir Nikishkin writes:
> However, the manual node you're pointing to disagrees with the claim that
> those are equivalent:
>
>>If you need both a repeater and a special warning period in a deadline
>>entry, the repeater should come first and the warning period last
>> DEADLINE:
Ah, great, thanks!
I have been looking at the wrong node all the time.
However, the manual node you're pointing to disagrees with the claim that
those are equivalent:
>If you need both a repeater and a special warning period in a deadline
>entry, the repeater should come first and the warning
Vladimir Nikishkin writes:
> I need to pay a fee by every 28th of the month, and I want this task
> to show up in the agenda from the 20th of the next not paid month.
>
> What's the proper DEADLINE format?
>
> DEADLINE: <2020-02-28 Sun .+1m -10d> ?
> DEADLINE: <2020-02-28 Sun -10d .+1m> ?
