>From 5437667a97dcd03a2993bfde93b0253590fae74a Mon Sep 17 00:00:00 2001 From: Robert Pluim Date: Fri, 10 Jun 2022 17:53:12 +0200 Subject: [PATCH] doc/org-manual.org: Reference org-cyclic and org-block * doc/org-manual.org (Footnotes): Add org-cyclic and org-block to note about org diary functions. Add function indices for org-{date, anniversary, cyclic, block}. --- doc/org-manual.org | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index 32a45f884..d560562c5 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -22046,6 +22046,10 @@ * Footnotes However, any date inserted or modified by Org adds that day name, for reading convenience. +#+findex: org-date +#+findex: org-anniversary +#+findex: org-cyclic +#+findex: org-block [fn:60] When working with the standard diary expression functions, you need to be very careful with the order of the arguments. That order depends evilly on the variable ~calendar-date-style~. For example, to @@ -22053,10 +22057,11 @@ * Footnotes =(diary-date 12 1 2005)= or =(diary-date 1 12 2005)= or =(diary-date 2005 12 1)=, depending on the settings. This has been the source of much confusion. Org mode users can resort to special versions of -these functions like ~org-date~ or ~org-anniversary~. These work just -like the corresponding ~diary-~ functions, but with stable ISO order -of arguments (year, month, day) wherever applicable, independent of -the value of ~calendar-date-style~. +these functions, namely ~org-date~, ~org-anniversary~, ~org-cyclic, and +~org-block~. These work just like the corresponding ~diary-~ +functions, but with stable ISO order of arguments (year, month, day) +wherever applicable, independent of the value of +~calendar-date-style~. [fn:61] See the variable ~org-read-date-prefer-future~. You may set that variable to the symbol ~time~ to even make a time before now -- 2.35.1.607.gf01e51a7cf