From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: please read: bug when marking tasks done Date: Tue, 15 Jan 2019 09:24:50 -0500 Message-ID: <87muo2hubx.fsf@norang.ca> 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> <87pnt2neeg.fsf@gnu.org> <87bm4kxqhn.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([209.51.188.92]:39531) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gjPeP-000864-P6 for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 09:25:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gjPeO-0008A6-Pl for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 09:25:09 -0500 Received: from outbound2m.ore.mailhop.org ([54.149.155.156]:59090) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gjPeN-00085J-Sg for emacs-orgmode@gnu.org; Tue, 15 Jan 2019 09:25:08 -0500 In-Reply-To: (Samuel Wales's message of "Sun, 13 Jan 2019 14:52:55 -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" To: Samuel Wales Cc: cesar mena , Leo Gaspard , emacs-orgmode Samuel Wales writes: > dunno best solution. > > another option is to comment out repeater intervals like ;.+2d instead > of .+0d or =[... .+2d]=. > > this would also allow you to know what the interval was [currently > that information is lost]. it would avoid overloading face. it would > be under user control for every ts. it would, however, require > updating ts regexp. > > > On 1/13/19, Nicolas Goaziou wrote: >> Hello, >> >> cesar mena writes: >> >>> 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] >> >> Thinking about it, another possibility is to add a variable, e.g., >> `org-repeat-inactive-timestamps', letting the user choose what to do >> with inactive time stamps. I think it would default to nil. >> >> This would be a more conservative solution; however, this would >> contradict releases notes for Org 9.2. >> >> WDYT? >> >> Regards, >> >> -- >> Nicolas Goaziou >> >> I don't have a need for updating any timestamps but the ones in the SCHEDULED/DEADLINE: entry. A variable to control behaviour would work great for me. Regards, Bernt