From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: please read: bug when marking tasks done Date: Sat, 12 Jan 2019 12:24:43 +0100 Message-ID: <87y37qxgn8.fsf@nicolasgoaziou.fr> References: <87d0paprs6.fsf@gnu.org> <87wonhcpnj.fsf@nicolasgoaziou.fr> <871s5o8pgf.fsf@gnu.org> <87muobcur7.fsf@nicolasgoaziou.fr> <87woneykuc.fsf@gnu.org> <87y37tzbrd.fsf@nicolasgoaziou.fr> <87muo88up0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:45589) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1giHPE-0007G9-3e for emacs-orgmode@gnu.org; Sat, 12 Jan 2019 06:24:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1giHPD-0005Kc-BE for emacs-orgmode@gnu.org; Sat, 12 Jan 2019 06:24:48 -0500 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:39233) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1giHPD-0005Js-5V for emacs-orgmode@gnu.org; Sat, 12 Jan 2019 06:24:47 -0500 In-Reply-To: <87muo88up0.fsf@gnu.org> (cesar mena's message of "Thu, 10 Jan 2019 09:15:55 -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: Leo Gaspard , emacs-orgmode Hello, cesar mena writes: > ok, so "current headline" is taken broadly. but what about the > deadline/scheduled part? what makes a time stamp "deadline/scheduled"? > those are the ones that should change as per the doc. You are right the docstring is inaccurate here. It is not limited to scheduled and deadlines, but also to plain time stamps. This is an important feature. However, this is not related to the commit we're talking about. > they're plain lists that haven't changed after they've been written. one > could use them for billing reports etc ... Of course. What I mean is Org has no way to know the meaning of the contents, or what you want to do with them, if you don't put markers or some special syntax somewhere. >> 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] > > that's not a bad idea, but what about the other way round? > > that is, inactive timestamps with repeaters do not update unless they are > marked as you suggest. this way current workflows are not affected and > inactive timestamps can be made to update if requested. The other way around is not possible because =...= means "verbatim". This would be contradictory. The main question is: what to do with an "inactive time stamp with repeater". The original report, that lead to the incriminated commit, emphasized the "repeater" part, arguing a repeater should induce the time stamp is meant to be repeated, notwithstanding its nature. You are emphasizing the "inactive" part of it, arguing that anything inactive should not change dynamically. Both arguments can be heard. I agree yours is more conservative. Yet, I'd like to hear about a solution than can satisfy both. I'm Cc'ing the OP. > yes, i see where you're coming from. i like to keep it simple. > > (setq org-for-mere-mortal t) I'm trying to keep Org as simple as possible, but different users have different use cases, and, in some annoying situations like this one, these use cases conflict. Regards, -- Nicolas Goaziou