emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Michaël Cadilhac" <michael@cadilhac.name>
Cc: Jack Kamm <jackkamm@gmail.com>,
	Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: ox-icalendar: Filter todo-types
Date: Sun, 23 Jun 2024 13:16:58 +0000	[thread overview]
Message-ID: <87v81zu7cl.fsf@localhost> (raw)
In-Reply-To: <CADt3fpOR9tuf=rcdRbH++=GaUGGLR71SHqwpOhd9X10bUgJPGw@mail.gmail.com>

Michaël Cadilhac <michael@cadilhac.name> writes:

>> > Perhaps we could have an option ox-icalendar-export-todo-keywords-as
>> > which could determine whether a keyword should be exported, and if so
>> > with what status, e.g.:
>> >
>> > (defcustom ox-icalendar-export-todo-keywords-as
>> >  '((no-export . ("SKIP"))
>> >    (cancelled . ("KILLED" "CANCELLED"))
>> >    (in-process . ("PROG"))))
> ...
>> Maybe we can expand the allowed values of `org-icalendar-include-todo' instead?
>
> I don't think this is the purpose of `include-todo', which seems to be
> specific to VTODO vs VEVENT.  Do you have something in mind that
> combines that feature with STATUS?

You are right that `org-icalendar-include-todo' is only affecting VTODO,
but not VEVENT.

My concern is mostly that "(no-export . ("SKIP"))" is somewhat similar
to `org-icalendar-include-todo' set to a list of todo keywords.  So, it
may be confused with VTODO-specific option.

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.

What is unique to icalendar exporter is the STATUS property. Having a
setting to set it according to todo keyword would indeed make sense.

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)?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-06-23 13:16 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 [this message]
2024-06-24  6:38         ` Jack Kamm
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=87v81zu7cl.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=jackkamm@gmail.com \
    --cc=michael@cadilhac.name \
    /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).