From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Rogers Subject: Re: [BUG?] org-clone-subtree-with-time-shift Date: Tue, 09 Apr 2013 11:03:47 -0700 Message-ID: <86txnf8tto.fsf@gmail.com> References: <86y5cr8vhq.fsf@gmail.com> <874nffoaz4.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPctc-0003eI-KV for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 14:03:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UPctb-0005RX-7f for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 14:03:52 -0400 Received: from mail-pb0-f42.google.com ([209.85.160.42]:64424) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPctb-0005RF-04 for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 14:03:51 -0400 Received: by mail-pb0-f42.google.com with SMTP id up7so350890pbc.15 for ; Tue, 09 Apr 2013 11:03:50 -0700 (PDT) In-Reply-To: <874nffoaz4.fsf@bzg.ath.cx> (Bastien's message of "Tue, 09 Apr 2013 19:44:15 +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 writes: > Hi David, > > David Rogers writes: > >> I like to use org-clone-subtree-with-time-shift (C-c C-x c) fairly >> frequently in some of my Org-mode files. Lately, it seems to have >> changed its function so that it creates only an exact clone, and doesn't >> prompt me for the time shift. Can other people reproduce this on a >> fairly recent git pull, or do I need to explore my .emacs to find out >> what I've done wrong? > > The default is to not ask for a time-shift by default, only when > (1) called with a prefix argument and (2) there is a time cookie. > > C-u C-c C-x c should do. > > Let me know if the docstring is not clear or if you find this not > user-friendly -- remember in many cases, we may want to clone tasks > that have no time specs. Is this something where the default has been changed recently? I'm fine with using a prefix, and it's not unfriendly; just this wasn't the way it worked before for me, so I assumed something was wrong. -- Thanks David