unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Andreas Gösele" <goesele@hfph.mwn.de>
To: help-gnu-emacs@gnu.org
Subject: Re: sexp and icalendar-export-file
Date: Mon, 24 May 2021 00:03:08 -0400	[thread overview]
Message-ID: <87im38u6bn.fsf@hfph.mwn.de> (raw)
In-Reply-To: 87sg2et7ei.fsf@hfph.mwn.de

Hi,

a follow up to my last post.

I tried whether a detour through org-mode could provide a
solution. Inspired by
https://mattduck.github.io/generic-css/demo/org-demo.html I created an
org file with the following contend:

** Class 8:15am-10:00am
   <%%(org-class 2021 1 1 2021 5 30 1 14)> Class

* Weekly meeting with boss
  <2021-01-19 Tue  14:00 +1w>

** Class 7:00pm-9:00pm
   <%%(and (= 1 (calendar-day-of-week date)) (diary-block 2 16 2021 4 20 2021))>

Executing "org-agenda a" results in an agenda view which includes the
first class entry and the Weekly meeting. The second Class entry doesn't
appear. I don't get any error messages.

When I execute "org-icalendar-export-agenda-files" I get an ics file
with only the Weekly meeting with the boss and an error message in the
*icalendar-errors* buffer:

Error in line 0 -- (end-of-file): ‘%%(and (= 1 (calendar-day-of-week date)) (diary-block 2 16 2021 4 20 2021)) Class 7:00pm-9:00pm’

I also get 14 times the warning:

Error (diary): Bad diary sexp at line 1 in ~/.emacs.d/diary:
(= 1 (calendar-day-of-week date)
Error: (end-of-file)

This is the same kind of warning I get when I try to export my diary
file with corresponding sexps directly. Is
"org-icalendar-export-agenda-files" using or build on
icalendar-export-file?

So, do I conclude correctly, that even using org-mode and its agenda
will not allow me to export more complicated sexps (the second Class one
doesn't even work with agenda views) or an org-class entry to an ics
file?

Thanks a lot

Andreas




  reply	other threads:[~2021-05-24  4:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23  4:12 sexp and icalendar-export-file Andreas Gösele
2021-05-24  4:03 ` Andreas Gösele [this message]
2021-05-24  7:03   ` Jean Louis
2021-05-24  7:11   ` Jean Louis
2021-05-24 10:52   ` Michael Heerdegen
2021-05-24 11:30     ` Michael Heerdegen
2021-05-24 19:13   ` Andreas Gösele

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87im38u6bn.fsf@hfph.mwn.de \
    --to=goesele@hfph.mwn.de \
    --cc=help-gnu-emacs@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.
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).