From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: icalendar event without description field fails on export
Date: Tue, 15 Oct 2019 09:10:35 +0100 [thread overview]
Message-ID: <87mue2juo4.fsf@ucl.ac.uk> (raw)
If I receive a calendar invite which has no description field, the
gnus-icalendar-event-export function fails with a nil string.
--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
#f(compiled-function (event reply-status) "Return string with new `org-mode' entry describing EVENT." #<bytecode 0x156bee96abd1>)(#<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
apply(#f(compiled-function (event reply-status) "Return string with new `org-mode' entry describing EVENT." #<bytecode 0x156bee96abd1>) #<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
gnus-icalendar-event->org-entry(#<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
gnus-icalendar:org-event-save(#<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
#f(compiled-function (event reply-status) #<bytecode 0x156bee6e19b1>)(#<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
apply(#f(compiled-function (event reply-status) #<bytecode 0x156bee6e19b1>) #<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
gnus-icalendar-event:sync-to-org(#<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330> nil)
gnus-icalendar-sync-event-to-org(#<gnus-icalendar-event-request gnus-icalendar-event-request-156bee49f330>)
gnus-icalendar-event-export()
funcall-interactively(gnus-icalendar-event-export)
call-interactively(gnus-icalendar-event-export nil nil)
command-execute(gnus-icalendar-event-export)
--8<---------------cut here---------------end--------------->8---
--
Eric S Fraga via Emacs 27.0.50 & org 9.2.4 on Debian bullseye/sid
next reply other threads:[~2019-10-15 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 8:10 Eric S Fraga [this message]
2019-10-15 9:51 ` Robert Pluim
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=87mue2juo4.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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 NNTP newsgroup(s).