emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Angel de Vicente <angel.vicente.garrido@gmail.com>,
Subject: Re: Timestamp with repeater interval AND END DATE?
Date: Fri, 10 Jun 2022 17:59:26 +0200	[thread overview]
Message-ID: <87ilp81pcx.fsf@gmail.com> (raw)
In-Reply-To: <87czfgr25x.fsf@localhost> (Ihor Radchenko's message of "Fri, 10 Jun 2022 23:03:38 +0800")

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

>>>>> On Fri, 10 Jun 2022 23:03:38 +0800, Ihor Radchenko <yantar92@gmail.com> said:

    Ihor> Robert Pluim <rpluim@gmail.com> writes:
    >> Ok. I will, or rather I would, but Iʼm obviously doing something wrong
    >> when building org:
    >> Debugger entered--Lisp error: (wrong-type-argument listp "Packages that conflict with Org mode")
    >> org-element-secondary-p(#("Conflicts" 0 9 (:parent (headline (:raw-value "Packages that conflict with Org mode" :begin 739020 :end 744524 :pre-blank 0 :contents-begin 739061 :contents-end 744523 :robust-begin 739148 :robust-end 744521 :level 3 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 1 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 739020 :DESCRIPTION "Packages that lead to conflicts." :ALT_TITLE "Conflicts" :title "Packages that conflict with Org mode" :parent (headline (:raw-value "Interaction with Other Packages" :begin 735540 :end 744524 :pre-blank 0 :contents-begin 735575 :contents-end 744523 :robust-begin 735658

    Ihor> Oops. It was not caught by tests. Fixed on main now. You can pull the
    Ihor> latest main. The error should disappear.

Working fine now, thanks. Doc patch attached (I have copyright
assignment on file for Emacs).



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-org-manual.org-Reference-org-cyclic-and-org-bloc.patch --]
[-- Type: text/x-diff, Size: 1990 bytes --]

From 5437667a97dcd03a2993bfde93b0253590fae74a Mon Sep 17 00:00:00 2001
From: Robert Pluim <rpluim@gmail.com>
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
 [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

  reply	other threads:[~2022-06-10 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 13:46 Timestamp with repeater interval AND END DATE? Angel de Vicente
2022-05-31 14:03 ` Eric S Fraga
2022-05-31 14:36   ` Angel de Vicente
2022-06-10  8:44     ` Robert Pluim
2022-06-10 11:27       ` Angel de Vicente
2022-06-10 12:45         ` Robert Pluim
2022-06-10 12:59           ` Ihor Radchenko
2022-06-10 14:24             ` Robert Pluim
2022-06-10 15:03               ` Ihor Radchenko
2022-06-10 15:59                 ` Robert Pluim [this message]
2022-06-11  4:51                   ` Ihor Radchenko
2022-06-10 14:37             ` Ambiguity in commit message conventions for org Robert Pluim
2022-06-10 15:11               ` Ihor Radchenko
2022-06-10 16:02                 ` Robert Pluim

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:

  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=87ilp81pcx.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=angel.vicente.garrido@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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).