all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Mark A. Hershberger" <mah@everybody.org>
To: 39782@debbugs.gnu.org
Subject: bug#39782: 28.0.50; gnus-icalendar does not understand multiple repeating days
Date: Tue, 25 Feb 2020 08:05:06 -0500	[thread overview]
Message-ID: <87r1yihl6l.fsf@everybody.org> (raw)


I used gnus-icalendar's "Export to Org" feature on an appointment, and
it successfully made a repeating entry (GOOD!) but failed to catch the
days other than the first one (BAD!).

The created org-entry contains the following RRULE entry:

    :RRULE:    FREQ=WEEKLY;UNTIL=20200519T133000Z;INTERVAL=1;BYDAY=MO,TU,WE,TH,FR;WKST=SU

The only entry created, though, was

    <2020-02-25 09:30-10:00 +1w>

I had to manually add the following entries:

  <2020-02-26 09:30-10:00 +1w>
  <2020-02-27 09:30-10:00 +1w>
  <2020-02-28 09:30-10:00 +1w>
  <2020-03-02 09:30-10:00 +1w>

From skimming gnus-icalendar.el and icalendar.el, it looks like the
"BYDAY" parsing in icalendar.el only looks for one day, instead of the
multiples given.  I think gnus-icalendar.el's export to org functions
are only set up to insert one day instead of the multiple times required
by this rule.





             reply	other threads:[~2020-02-25 13:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 13:05 Mark A. Hershberger [this message]
2020-07-19 13:58 ` bug#39782: 28.0.50; gnus-icalendar does not understand multiple repeating days Lars Ingebrigtsen
2020-07-19 15:36   ` Mark A. Hershberger
2020-07-19 16:03   ` Mark A. Hershberger
2020-07-20  9:56     ` Lars Ingebrigtsen
2020-07-20 10:16       ` Jan Tatarik
2020-07-31 11:39       ` Jan Tatarik
2020-08-21 16:03         ` Mark A. Hershberger
2020-08-22 13:39           ` Lars Ingebrigtsen
2020-08-22 21:25             ` Glenn Morris
2020-08-22 21:35               ` Lars Ingebrigtsen
2020-08-24 19:11 ` Mattias Engdegård
2020-08-26  8:54   ` Mattias Engdegård

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1yihl6l.fsf@everybody.org \
    --to=mah@everybody.org \
    --cc=39782@debbugs.gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.