From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: please read: bug when marking tasks done Date: Wed, 09 Jan 2019 23:50:30 +0100 Message-ID: <87y37tzbrd.fsf@nicolasgoaziou.fr> References: <87d0paprs6.fsf@gnu.org> <87wonhcpnj.fsf@nicolasgoaziou.fr> <871s5o8pgf.fsf@gnu.org> <87muobcur7.fsf@nicolasgoaziou.fr> <87woneykuc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:41561) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ghMgJ-00080L-Et for emacs-orgmode@gnu.org; Wed, 09 Jan 2019 17:50:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ghMgI-0006xS-AV for emacs-orgmode@gnu.org; Wed, 09 Jan 2019 17:50:39 -0500 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:55027) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ghMgI-0006uX-3p for emacs-orgmode@gnu.org; Wed, 09 Jan 2019 17:50:38 -0500 In-Reply-To: <87woneykuc.fsf@gnu.org> (cesar mena's message of "Tue, 08 Jan 2019 15:07:23 -0500") 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" To: cesar mena Cc: emacs-orgmode Hello, cesar mena writes: > from the docstring: > > |----------- org-auto-repeat-maybe -------------------------------- > | Check if the *current headline* contains a repeated time-stamp. > | > | If yes, set TODO state back to what it was and change the base date > | of repeating *deadline/scheduled time stamps to new date* > | > | ... > |----------------------------------------------------------------- > > thus we should not programmatically modify an arbitrary date in a > document just because it has a repeater. specially not one buried 300 > lines deep in a :LOGBOOK: drawer. > > commit af81211fdc contradicts the established documentation. No, it doesn't. "current headline" is to be taken broadly, i.e., in the headline or the adjacent section. So, it doesn't matter if a time stamp is buried somewhere in the section: it is meant to be updated. Note that it was already the case for active time stamps before said commit. > but the solution overreaches. I agree the current state is not ideal, but as I said, the only suggestion I had was not satisfying. I'm all ears, though. > apologies if i wasn't clear. what should be immutable is a logged, > state-change entry. For Org syntax, there is no such thing as a state-change entry. They are just plain lists. You could write anything in them. Now, we might make its contents by marking them as verbatim, for example. E.g., - Rescheduled from =[2019-02-05 Tue .1m]= on [2018-09-29 Sat 18:50] > an existing entry should not change because one marks a task as DONE. I disagree. This has always been the case, at least for active time-stamps. Regards, -- Nicolas Goaziou