|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#13750: closed (23.4; icalendar export and XXpm time format) |
Date: | Wed, 06 Aug 2014 18:23:02 +0000 |
Your message dated Wed, 06 Aug 2014 20:21:57 +0200 with message-id <address@hidden> and subject line Re: bug#13750: 23.4; icalendar export and XXpm time format has caused the debbugs.gnu.org bug report #13750, regarding 23.4; icalendar export and XXpm time format to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 13750: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13750 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: 23.4; icalendar export and XXpm time format Date: Mon, 18 Feb 2013 00:00:01 -0800 User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.8 Emacs/23.4 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) ICALENDAR-EXPORT-FILE, when called on a file containing the single line 02/18/2013 3pm-4pm overlapping event 2 yields a single exported vevent: BEGIN:VEVENT UID:emacs2076943879932075328 DTSTART;VALUE=DATE:20130218 DTEND;VALUE=DATE:20130219 SUMMARY:3pm-4pm overlapping event 2 END:VEVENT The exported event should containg the time data in the appropriate location: BEGIN:VEVENT UID:emacs2076949831770903376 DTSTART;VALUE=DATE-TIME:20130218T150000 DTEND;VALUE=DATE-TIME:20130218T160000 SUMMARY:overlapping event 2 END:VEVENT Note that DIARY-ENTRY-TIME reads the string (sans date component) fine: ELISP> (diary-entry-time " 3pm-4pm overlapping event 2") 1500
--- End Message ---
--- Begin Message ---Subject: Re: bug#13750: 23.4; icalendar export and XXpm time format Date: Wed, 06 Aug 2014 20:21:57 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) Thanks for reporting. Fixed in trunk rev. 117656.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |