From: Robert Pluim <rpluim@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: icalendar event without description field fails on export
Date: Tue, 15 Oct 2019 11:51:58 +0200 [thread overview]
Message-ID: <m24l0a49q9.fsf@gmail.com> (raw)
In-Reply-To: <87mue2juo4.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 15 Oct 2019 09:10:35 +0100")
>>>>> On Tue, 15 Oct 2019 09:10:35 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:
Eric> If I receive a calendar invite which has no description field, the
Eric> gnus-icalendar-event-export function fails with a nil string.
Ah yes, I guess this is my fault. Does the following work for you?
diff --git a/lisp/gnus/gnus-icalendar.el b/lisp/gnus/gnus-icalendar.el
index e4779f52c0..77e73e6606 100644
--- a/lisp/gnus/gnus-icalendar.el
+++ b/lisp/gnus/gnus-icalendar.el
@@ -485,7 +485,7 @@ gnus-icalendar-event->org-entry
(narrow-to-region (point) (point))
(insert (gnus-icalendar-event:org-timestamp event)
"\n\n"
- description)
+ (or description "No description"))
(indent-region (point-min) (point-max) 2)
(fill-region (point-min) (point-max)))
next prev parent reply other threads:[~2019-10-15 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 8:10 Eric S Fraga
2019-10-15 9:51 ` Robert Pluim [this message]
2019-10-15 13:14 ` Eric S Fraga
2019-10-16 6:15 ` Robert Pluim
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=m24l0a49q9.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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 NNTP newsgroup(s).