From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Bug: org-clone-subtree-with-time-shift shifts CREATED property Date: Tue, 4 Oct 2011 17:32:26 +0200 Message-ID: <2011-10-04T17-27-01@devnull.Karl-Voit.at> 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]:47364) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB6zB-0008Bt-72 for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 11:32:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RB6z7-0002Ov-6W for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 11:32:49 -0400 Received: from lo.gmane.org ([80.91.229.12]:35770) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB6z6-0002Op-UA for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 11:32:45 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RB6z4-00021a-6A for emacs-orgmode@gnu.org; Tue, 04 Oct 2011 17:32:42 +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, 04 Oct 2011 17:32:42 +0200 Received: from news1142 by mail.michael-prokop.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Oct 2011 17:32:42 +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 Hi! When an entry got processed by org-clone-subtree-with-time-shift, its :CREATED: property gets shifted too: #+begin_example * <2011-10-04 Tue> test SCHEDULED: <2011-10-05 Wed> :PROPERTIES: :CREATED: <2011-10-04 Tue 17:27> :END: * <2011-10-11 Tue> test SCHEDULED: <2011-10-12 Wed> :PROPERTIES: :CREATED: <2011-10-11 Tue 17:27> :END: #+end_example Although this *might* be on purpose, I strongly argue to stop this behaviour because of: * the entry is not really created in the future. It is created either at the original :CREATED: timestamp _or_ it is created at the timestamp when org-clone-subtree-with-time-shift is executed. * the user gets heavily irritated when the generated entries keep popping up on future days. I suggest that at least for :CREATED: properties, the time stamp does not get changed by org-clone-subtree-with-time-shift. -- Karl Voit