From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Re: Bug: org-time-stamp loses repeater interval Date: Tue, 28 Jun 2011 15:40:10 +0200 Message-ID: <2011-06-28T15-28-18@devnull.Karl-Voit.at> References: <2011-06-24T16-30-43@devnull.Karl-Voit.at> <8772.1308931315@alphaville.dokosmarshall.org> <2011-06-26T13-23-38@devnull.Karl-Voit.at> <8739ivw8e8.fsf@gnu.org> Reply-To: news1142@Karl-Voit.at Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:53696) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbYWj-00059Y-GB for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 09:40:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbYWh-0004Rs-HJ for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 09:40:29 -0400 Received: from lo.gmane.org ([80.91.229.12]:58083) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbYWg-0004Rg-S4 for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 09:40:27 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QbYWd-00047r-3X for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 15:40:23 +0200 Received: from mail.michael-prokop.at ([88.198.6.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Jun 2011 15:40:23 +0200 Received: from news1142 by mail.michael-prokop.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Jun 2011 15:40:23 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org * Bastien wrote: > Karl Voit writes: > >> Same to me. Unfortunately I am using timestamps not only in the >> context of DEADLINE or SCHEDULED but also for events that should >> simply show up on the agenda (without deadline or scheduled >> timestamp at all). >> >> To me this *is* a bug since my expected behavior of org-time-stamp >> to modify an existing timestamp is different. > > It is now fixed in the latest git version. Please test and report, > if possible. I checked out d7c693c1ffe2ebf38604dd30fdd2f9d51a1c44d0 which should fix the problem and tested with «Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-04-04 on rothera, modified by Debian» and «Org-mode version 7.5 (release_7.5.462.gd7c69)» created timestamp with «C-c .» <2011-06-28 Tue> modified with «C-c.» to wednesday: <2011-06-29 Wed> manually added repeater: <2011-06-29 Wed +1w> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> repeater is lost :-( created another one with warning period: <2011-06-28 Tue -1d> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> warning period is lost :-( created another one with repeater and warning period: <2011-06-28 Tue +1w -1d> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> repeater and warning period is lost :-( -- Karl Voit