From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)] Date: Wed, 16 Mar 2016 22:11:04 +0100 Message-ID: <87vb4mw2l3.fsf@nicolasgoaziou.fr> References: <87a8m8nv3q.fsf@felesatra.moe> <87d1r2ll2q.fsf@nicolasgoaziou.fr> <87d1r1iomh.fsf@jakuri.lan> <87fuvum9v8.fsf@nicolasgoaziou.fr> <87d1qwzbvl.fsf@jakuri.felesatra.moe> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59165) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agIgf-00044F-Gs for emacs-orgmode@gnu.org; Wed, 16 Mar 2016 17:09:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1agIgc-0006l3-B2 for emacs-orgmode@gnu.org; Wed, 16 Mar 2016 17:09:01 -0400 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:59171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agIgc-0006kx-56 for emacs-orgmode@gnu.org; Wed, 16 Mar 2016 17:08:58 -0400 In-Reply-To: <87d1qwzbvl.fsf@jakuri.felesatra.moe> (Allen Li's message of "Mon, 14 Mar 2016 19:57:34 -0700") 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: Allen Li Cc: emacs-orgmode@gnu.org Hello, Allen Li writes: > I can think of three reasonable options: > > 1. Prompt for a note, then apply it to all affected items. > 2. Prompt for a note, then apply it only to items that are already > scheduled (and hence rescheduled). > 3. Don't attempt to add a note and just add timestamps. > > Then there's the unreasonable option: > > 4. Prompt for a note for each item. No worries. This is not possible without rewriting a large part of the log notes innards. > If I had to pick, I'd go with 2, but any of 1-3 is fine. In this case, > having bulk scheduling work is more important than whether > org-log-reschedule is being faithfully applied, in my opinion. It is fixed, with option 3. Global note doesn't sound like a silver bullet. Also, 3 was much easier to implement. Thank you for the feedback. Regards, -- Nicolas Goaziou