From: Jack Kamm <jackkamm@gmail.com>
To: "Ihor Radchenko" <yantar92@posteo.net>,
"Michaël Cadilhac" <michael@cadilhac.name>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: ox-icalendar: Filter todo-types
Date: Sun, 23 Jun 2024 23:38:56 -0700 [thread overview]
Message-ID: <87a5jaalq7.fsf@gmail.com> (raw)
In-Reply-To: <87v81zu7cl.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Another concern is that we already have `org-export-with-tasks' where
> you can specify which todo keywords should be exported and which
> headings should be exported, according to their todo keyword. So,
> "no-export" appears to unnecessary.
That's a good point. Michael, does `org-export-with-tasks' suffice for
your original need/request?
> However, after I looked at the RFC in more details now, I can see that
> the values of STATUS property depend on the entry type:
>
> statvalue-event = "TENTATIVE" ;Indicates event is tentative.
> / "CONFIRMED" ;Indicates event is definite.
> / "CANCELLED" ;Indicates event was cancelled.
> ;Status values for a "VEVENT"
>
> statvalue-todo = "NEEDS-ACTION" ;Indicates to-do needs action.
> / "COMPLETED" ;Indicates to-do completed.
> / "IN-PROCESS" ;Indicates to-do in process of.
> / "CANCELLED" ;Indicates to-do was cancelled.
> ;Status values for "VTODO".
>
> statvalue-jour = "DRAFT" ;Indicates journal is draft.
> / "FINAL" ;Indicates journal is final.
> / "CANCELLED" ;Indicates journal is removed.
> ;Status values for "VJOURNAL".
>
> Maybe we can introduce separate variables mapping todo keyword to status
> depending on the entry type (VTODO vs. VEVENT; we do not export VJOURNAL)?
Sure, but we should also consider the STATUS for VEVENTs created from
non-TODO entries.
Perhaps these variables could map tags as well as todo keywords to
status? E.g., in the following:
(setq org-icalendar-event-status-map
'((cancelled . ("KILLED" "cancelled"))))
Then any VEVENT created from entries whose todo-keyword or tag matches
the above would have STATUS set to CANCELLED. For example, both of the
following entries would contain VEVENTs exported as such:
* An event that was cancelled :cancelled:
A non-todo entry with active timestamp <2024-06-23>.
It will be exported with STATUS as CANCELLED.
* KILLED A todo that was cancelled
SCHEDULED: <2024-06-22>
This todo entry has both a scheduling timestamp as well as an active
timestamp <2024-06-23>, and may create both VEVENT and VTODO. Any
VEVENTs created will have STATUS as CANCELLED, due to "KILLED" being
in org-icalendar-event-status-map. Any VTODO created will have STATUS
set according to org-icalendar-todo-status-map instead.
next prev parent reply other threads:[~2024-06-24 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 16:33 ox-icalendar: Filter todo-types Michaël Cadilhac
2024-06-22 23:28 ` Jack Kamm
2024-06-23 11:27 ` Ihor Radchenko
2024-06-23 12:03 ` Michaël Cadilhac
2024-06-23 13:16 ` Ihor Radchenko
2024-06-24 6:38 ` Jack Kamm [this message]
2024-06-24 7:23 ` Ihor Radchenko
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5jaalq7.fsf@gmail.com \
--to=jackkamm@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael@cadilhac.name \
--cc=yantar92@posteo.net \
/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
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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).