From: Jude DaShiell <firstname.lastname@example.org>
Subject: likely re-order date problem solution
Date: Fri, 16 Jul 2021 11:19:57 -0400 [thread overview]
Message-ID: <alpine.NEB.email@example.com> (raw)
I think I figured out how to make re-order dates work in orgmode.
The start date is the date when items start getting used. So subtract the
number of weeks before the next order is needed from the start date and
write that time stamp in with a + repeater value to cover the days until
the next order. You get back your start date with a repeater. So copy
that time stamp down and so long as the repeater continues to work you
should get a series of dates matching your re-order date requirements.
There may be an easier way to do this in orgmode but I haven't run across
that one yet.
reply other threads:[~2021-07-16 15:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).