From mboxrd@z Thu Jan 1 00:00:00 1970 From: cesar mena Subject: Re: please read: bug when marking tasks done Date: Sat, 12 Jan 2019 09:23:19 -0500 Message-ID: <87pnt2neeg.fsf@gnu.org> 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> <87y37qxgn8.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:49402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1giKS0-00081F-OG for emacs-orgmode@gnu.org; Sat, 12 Jan 2019 09:39:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1giKC4-00085a-09 for emacs-orgmode@gnu.org; Sat, 12 Jan 2019 09:23:24 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:41063) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1giKC3-00084y-M6 for emacs-orgmode@gnu.org; Sat, 12 Jan 2019 09:23:23 -0500 In-Reply-To: <87y37qxgn8.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 12 Jan 2019 12:24:43 +0100") 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: emacs-orgmode Cc: Leo Gaspard hello, Nicolas Goaziou writes: >>> 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. i see. i didn't know =...= meant verbatim. so in light of this new knowledge :) your solution makes a lot of sense. i was originally opposed to it because it means current documents will have to change to add =...= but in the end it seems the simplest. > 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. i'm ok going with the verbatim syntax - rescheduled lines will now look like (w/o the double quotes?): - Rescheduled from =[2019-02-05 Tue .1m]= on [2018-09-29 Sat 18:50] > 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. we are ever grateful. best, -cm