From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Ulf Jasper Newsgroups: gmane.emacs.bugs Subject: bug#33277: 25.1; icalendar-import-file incorrectly imports events with same start/end time Date: Thu, 05 Sep 2019 21:32:04 +0200 Message-ID: <871rwuy1xn.fsf@panama> References: <87muqnz8ib.fsf@berkeley.edu> <87wogq3uj7.fsf@mouse.gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="190656"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) Cc: 33277@debbugs.gnu.org, Stefan van der Walt To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Sep 05 21:33:27 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1i5xVX-000nUP-3h for geb-bug-gnu-emacs@m.gmane.org; Thu, 05 Sep 2019 21:33:27 +0200 Original-Received: from localhost ([::1]:49246 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i5xVV-0006CX-MG for geb-bug-gnu-emacs@m.gmane.org; Thu, 05 Sep 2019 15:33:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47741) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i5xV9-00069a-Rn for bug-gnu-emacs@gnu.org; Thu, 05 Sep 2019 15:33:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i5xV8-0005dG-P7 for bug-gnu-emacs@gnu.org; Thu, 05 Sep 2019 15:33:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55511) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i5xV8-0005d8-IW for bug-gnu-emacs@gnu.org; Thu, 05 Sep 2019 15:33:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i5xV8-0000l9-DH for bug-gnu-emacs@gnu.org; Thu, 05 Sep 2019 15:33:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ulf Jasper Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 05 Sep 2019 19:33:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33277 X-GNU-PR-Package: emacs Original-Received: via spool by 33277-submit@debbugs.gnu.org id=B33277.15677119472855 (code B ref 33277); Thu, 05 Sep 2019 19:33:02 +0000 Original-Received: (at 33277) by debbugs.gnu.org; 5 Sep 2019 19:32:27 +0000 Original-Received: from localhost ([127.0.0.1]:36098 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1i5xUY-0000jz-W1 for submit@debbugs.gnu.org; Thu, 05 Sep 2019 15:32:27 -0400 Original-Received: from mout.web.de ([212.227.17.12]:44721) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1i5xUV-0000jT-TL for 33277@debbugs.gnu.org; Thu, 05 Sep 2019 15:32:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1567711936; bh=gD9YvFQWJUxZh80k0sIvhiO9cMtyHwKyW2vSCaYAkjk=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=PJFz9RdBiYfHyv5llU1XXLvLeeEHXtKkwd5jds7GXmwvEDR4Q1JkDHRjTUDHpyDFn VeejsdktRuj43+dOkvorRV/HQr2yJAq8cMrwkm2NRH9M4l+H4iPMXy5KDQdB5H4E3d xXdIay3rJ/nFULzLNSsdLCiWkVjbqlgcy/waKK2c= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from udesktop ([87.158.226.27]) by smtp.web.de (mrweb103 [213.165.67.124]) with ESMTPSA (Nemesis) id 0MIeYe-1i8APo2dZ2-002JvI; Thu, 05 Sep 2019 21:32:16 +0200 In-Reply-To: <87wogq3uj7.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Wed, 10 Jul 2019 15:10:04 +0200") X-Provags-ID: V03:K1:YTPVuOJkPIt/vFUEip1oHNWKjimHNUHLCp/LPPhTL3uknpf3Jwp HB28FyrZhYdlQMeUWq/RdJPGsQ/KVL/ECW+znK1WKYp/tQy+EZOjm+cNrL1DdGTOXPnBWRH BFReDDSYvOhXLKk5jvENEK76woDijcF13hR1zlIg1znZ2wFw3+PhjPHZClmy3Gdeqfbe7u8 azaiG3fN+zitOD190mxRA== X-UI-Out-Filterresults: notjunk:1;V03:K0:N/qlOTKym+g=:TRB7V8NSGpszYCoL9yLvy2 ixSKJFRDSngtfw4WzIYdW/B0nebn1T2xXXyjdWjyv6LO+i/Of9Y1rcdGlHrqRkGpSQhtMPdfe Nieu5dutgpzydONJG36liM8ur361Bh2dt7ly9hysHHEJHA3Qe1e4C9PF2WR8V81NxyrHalWr3 ReZoNaR1QYCvkWRI0PBtTENSvopX1FvfNWjCHXcV0xcaQFqexkRhDo6e7MMsmpH4gQsUDo+U0 Ndvmo+sme99Igc3FDOLg27MA+10isE/OrxKCf2Egfdy9wXq5wYVSKYY3apTBQ/3w4hgl2v+op Dpl0n/3pUB24p4cLRWyDDjt7+NIRb7aSh1fbtYy4iAeDYZb1C4tpAjHWc7NlJaZLJeldIGtRe cum3U4vbhV2PCSb+Lo6fBfLAo6kgqyWLOGoWQeMz3h+j0SS1LxaaimRL8ibpIRkPEx3h1cpOJ drTqP6o1X2iALbOHpXaOAbME5io//LFy7JeXCVT2AQ2BhkeDpvY3Mkl9oMOKq/9PLamsfHiWB agfu6HA+eYtPENwLdSF+DeyL0uN/fK6PLEwpkn0iVsJHhZgOhIap0QBnlWlxcZo0CHLXtUoax cVc8QGC1Eq5l0qesE0zhyBzrqRmkOAFN/MV6mQmpH7KpfcBlNaTi67W9tiTaerfWJ2SkEGVSU tF2jScjjTt8JHh1FUDCjDYh7a1La7MV7CYTgF6bmDVWbra5Fy3aaKb5o+BVs73cIaXVNp5lmy R6/qiTOhi++9hdr4dNcVBI5WYr0rrqAoZaSB/+0hJRUUyTIRwcCbQUypyZ0S5w6Uuey5n+Xr X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:166235 Archived-At: Am 10.07.2019 um 15:10 (+0200) schrieb Lars Ingebrigtsen: > Stefan van der Walt writes: > >> When importing an ical file containing an event with the same start and >> end time, that event is converted to an all-day event. > > [...] > >> I import it using: >> >> (icalendar-import-file "/tmp/basic.ics" "/tmp/basic.diary") >> >> And in basic.diary see: >> >> 11/5/2018 event with same start/end time > > But is that the same as an all-day event? > >> Instead of: >> >> 11/5/2018 12:00-12:00 > > Yes, that would be more logical... > >> The source code (icalendar.el) mentions the following: >> >> ;; Please note: >> ;; - Diary entries which have a start time but no end time are assumed to >> ;; last for one hour when they are exported. >> >> Still, then I would expect the diary entry to be: >> >> 11/5/2018 12:00-13:00 This note is about export, i.e. diary to ical. > > This seems to all be very inconsistent. I rarely use diary myself, but > what would users expect here? Exporting the event with 12:00-12:00 > would be consistent, at least. I'll have a look.