Gnus development mailing list
 help / color / mirror / Atom feed
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: Wed, 16 Oct 2019 08:15:54 +0200	[thread overview]
Message-ID: <m2o8yh2p2d.fsf@gmail.com> (raw)
In-Reply-To: <87lftmxiar.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 15 Oct 2019 14:14:04 +0100")

>>>>> On Tue, 15 Oct 2019 14:14:04 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:

    Eric> On Tuesday, 15 Oct 2019 at 11:51, Robert Pluim wrote:
    >>>>>>> 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?

    Eric> Your fix did the job.  Thanks.

Thanks for testing. Fixed in emacs master.

Robert



      reply	other threads:[~2019-10-16  6:15 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
2019-10-15 13:14   ` Eric S Fraga
2019-10-16  6:15     ` Robert Pluim [this message]

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=m2o8yh2p2d.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).