emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Angel de Vicente <angel.vicente.garrido@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Timestamp with repeater interval AND END DATE?
Date: Fri, 10 Jun 2022 14:45:33 +0200	[thread overview]
Message-ID: <87v8t81yc2.fsf@gmail.com> (raw)
In-Reply-To: <87wndoahd0.fsf@gmail.com> (Angel de Vicente's message of "Fri, 10 Jun 2022 12:27:23 +0100")

>>>>> On Fri, 10 Jun 2022 12:27:23 +0100, Angel de Vicente <angel.vicente.garrido@gmail.com> said:

    >> If you use `org-cyclic' and `org-block' you donʼt need to worry about
    >> that anymore.

    Angel> I tried (briefly :-)) to look for some place where org-cyclic and
    Angel> org-block are documented, but failed. But I tried, and they do work
    Angel> nicely. So they always assume 'iso' style regardless of the value of
    Angel> 'calendar-date-style'? 

Yes. They donʼt appear in the info documentation anywhere that I can
see. Thereʼs a footnote in (info "(org) Weekly/daily agenda") about
`org-anniversary' and `org-date' though.

I can send a patch against the org-mode repository main branch, or fix
it directly in the emacs repo. What's the preferred workflow for this
kind of change?


  reply	other threads:[~2022-06-10 12:48 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 [this message]
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
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=87v8t81yc2.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=angel.vicente.garrido@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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