From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to properly set up reminders for paying cellphone fees in org?
Date: Thu, 30 Apr 2020 14:22:08 +0800 [thread overview]
Message-ID: <CA+A2iZb_cfap6vacwgJYWB+xvN_=CF=dvSKK2CepKZU_98AHhQ@mail.gmail.com> (raw)
In-Reply-To: <87imhh4lc7.fsf@kyleam.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
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 period last
> DEADLINE: <2005-10-01 Sat +1m -3d>
However, the manual may be incomplete.
Thank you, problem seems to be solved.
Kyle Meyer <kyle@kyleam.com> 於 2020年4月30日 週四 13:02 寫道：
> Vladimir Nikishkin <lockywolf@gmail.com> 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> ?
>
> Those are equivalent. Though you might consider whether you'd prefer
> '+' or '++' for this rather than '.+'. See (info "(org)Repeated tasks")
> if you're not aware of the differences.
>
> 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 [...]
>
[-- Attachment #2: Type: text/html, Size: 1949 bytes --]
next prev parent reply other threads:[~2020-04-30 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 4:19 How to properly set up reminders for paying cellphone fees in org? Vladimir Nikishkin
2020-04-30 5:02 ` Kyle Meyer
2020-04-30 6:22 ` Vladimir Nikishkin [this message]
2020-04-30 22:04 ` Kyle Meyer
2020-05-02 7:37 ` Marcin Borkowski
2020-05-02 8:12 ` tomas
2020-05-02 11:46 ` Marcin Borkowski
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='CA+A2iZb_cfap6vacwgJYWB+xvN_=CF=dvSKK2CepKZU_98AHhQ@mail.gmail.com' \
--to=lockywolf@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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).