From: Kyle Meyer <firstname.lastname@example.org> To: Dieter Faulbaum <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] repeat cookies should be in the same order as the repeats Date: Tue, 10 Nov 2020 00:49:26 -0500 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Thanks for the patch. > [PATCH] repeat cookies should be in the same order as the repeats Convention nit: Ideally this subject would start with a "scope/file:", e.g. "manual:" or "org-manual.org:". Also, could you please add a changelog entry and TINYCHANGE cookie, as described at <https://orgmode.org/worg/org-contribute.html>? Dieter Faulbaum writes: > --- > doc/org-manual.org | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/doc/org-manual.org b/doc/org-manual.org > index ef2dad9ef..e78690993 100644 > --- a/doc/org-manual.org > +++ b/doc/org-manual.org > @@ -5741,6 +5741,7 @@ expressions to process these values before inserting them into a table > or a dynamic block. > > * Dates and Times > + > :PROPERTIES: > :DESCRIPTION: Making items useful for planning. > :END: Please drop this unrelated change. > @@ -6281,7 +6282,7 @@ organize such tasks using a so-called repeater in a =DEADLINE=, > the =+1m= is a repeater; the intended interpretation is that the task > has a deadline on =<2005-10-01>= and repeats itself every (one) month > starting from that time. You can use yearly, monthly, weekly, daily > -and hourly repeat cookies by using the =y=, =w=, =m=, =d= and =h= > +and hourly repeat cookies by using the =y=, =m=, =w=, =d= and =h= > letters. 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 Good catch. Thanks.
next prev parent reply other threads:[~2020-11-10 5:49 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-04 14:35 Dieter Faulbaum 2020-11-10 5:49 ` Kyle Meyer [this message] 2020-11-20 4:16 ` Kyle Meyer
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://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ email@example.com public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git