unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: sexp and icalendar-export-file
Date: Mon, 24 May 2021 12:52:55 +0200	[thread overview]
Message-ID: <87h7isjtdk.fsf@web.de> (raw)
In-Reply-To: 87im38u6bn.fsf@hfph.mwn.de

Andreas Gösele <goesele@hfph.mwn.de> writes:

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

I can only answer that org related part of the question: if you want to
let special diary entries appear in the agenda, these _must_ evaluate to
a string (or nil), and that string will be used as headline displayed in
the agenda.  The given headline is silently ignored, AFAIK.  The
advantage is that you can generate headlines dynamically in the diary
sexp.

Org could be smarter and use the given static headline when the diary
sexp returns a non-nil value that is not a string, but that isn't the
case, unfortunately.

I only know that because I asked the question in the org mailing list,
some months ago.  You might look there for the answers I got for more
background.

I dunno whether this also effects icalendar export.


Regards,

Michael.




  parent reply	other threads:[~2021-05-24 10:52 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
2021-05-24  7:03   ` Jean Louis
2021-05-24  7:11   ` Jean Louis
2021-05-24 10:52   ` Michael Heerdegen [this message]
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=87h7isjtdk.fsf@web.de \
    --to=michael_heerdegen@web.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).