From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Re: Bug: org-time-stamp loses repeater interval Date: Sun, 26 Jun 2011 13:30:35 +0200 Message-ID: <2011-06-26T13-23-38@devnull.Karl-Voit.at> References: <2011-06-24T16-30-43@devnull.Karl-Voit.at> <8772.1308931315@alphaville.dokosmarshall.org> Reply-To: news1142@Karl-Voit.at Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:40989) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QanYF-0000p7-Ts for emacs-orgmode@gnu.org; Sun, 26 Jun 2011 07:30:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QanYE-0005vW-TC for emacs-orgmode@gnu.org; Sun, 26 Jun 2011 07:30:55 -0400 Received: from lo.gmane.org ([80.91.229.12]:49229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QanYE-0005vQ-NX for emacs-orgmode@gnu.org; Sun, 26 Jun 2011 07:30:54 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QanY8-00050t-NP for emacs-orgmode@gnu.org; Sun, 26 Jun 2011 13:30:48 +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 ; Sun, 26 Jun 2011 13:30:48 +0200 Received: from news1142 by mail.michael-prokop.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Jun 2011 13:30:48 +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 * Michael Brand wrote: > > If it is a DEADLINE or SCHEDULED you can also use "C-c C-d ." or "C-c > C-s ." as a workaround to preserve the repeater. Therefore I consider > loosing the repeater with just "C-c ." on any active timestamp, no > matter if a DEADLINE, SCHEDULED or not, a bug. 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. So, how reaches this bug report a person who is able to fix it? PS: Sorry, I still don't know ELISP yet and therefore can't fix it by myself. -- Karl Voit