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.
