From: Rajeev Narang via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 37887@debbugs.gnu.org
Subject: bug#37887: 27.0.50; icalendar-export-region: multiline Desc not handled
Date: Tue, 25 Aug 2020 21:13:16 -0400 [thread overview]
Message-ID: <87lfi2ky4z.fsf@hm.sivalik.com> (raw)
In-Reply-To: <CADwFkmngUCpir5UdOjV-ynr-s89NpM6kBsMGj1tJW2wGHZPZ8Q@mail.gmail.com> (Stefan Kangas's message of "Tue, 25 Aug 2020 16:43:28 -0700")
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
If you import the attached file (icalendar-import-file) and then export it back (icalendar-export-file) you will see that the Desc is lost in the re-export.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: t0.ics --]
[-- Type: text/calendar, Size: 587 bytes --]
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
BEGIN:VEVENT
DTSTART:20200822T180000Z
DTEND:20200822T190000Z
DTSTAMP:20200825T203517Z
CREATED:20200822T180043Z
DESCRIPTION:To see detailed information for automatically created events li
ke this one\, use the official Google Calendar app. https://g.co/calendar\n
\nThis event was created from an email you received in Gmail. https://mail.
google.com/mail?extsrc=cal&plid=ACUX6DPSxIW80hA4eZMPB6pDuC8RNU1IYLQ\n
LAST-MODIFIED:20200822T180043Z
SEQUENCE:0
SUMMARY:Reservation at Place
END:VEVENT
END:VCALENDAR
next prev parent reply other threads:[~2020-08-26 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:58 bug#37887: 27.0.50; icalendar-export-region: multiline Desc not handled Rajeev Narang via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-01 9:40 ` Eli Zaretskii
2020-08-25 23:43 ` Stefan Kangas
2020-08-26 1:13 ` Rajeev Narang via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-08-11 12:58 ` Lars Ingebrigtsen
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=87lfi2ky4z.fsf@hm.sivalik.com \
--to=bug-gnu-emacs@gnu.org \
--cc=37887@debbugs.gnu.org \
--cc=rajeev+jnk@sivalik.com \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).