From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: [bug] timed repeater shows up in wrong place Date: Mon, 28 Nov 2016 15:20:15 -0700 Message-ID: References: <87inrxo5yt.fsf@cmena.pobox.com> <87a8d8o0rv.fsf@cmena.pobox.com> <878tsqfhoo.fsf@nicolasgoaziou.fr> <87h97bqor9.fsf@nicolasgoaziou.fr> <878tsnq7kl.fsf@nicolasgoaziou.fr> <87k2bstlyg.fsf@nicolasgoaziou.fr> <874m2w0zyt.fsf@nicolasgoaziou.fr> <87wpfqfrv5.fsf@nicolasgoaziou.fr> <87r35xgon4.fsf@nicolasgoaziou.fr> <87vav8fnes.fsf@nicolasgoaziou.fr> <87r35wf47l.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBUHb-00043N-51 for emacs-orgmode@gnu.org; Mon, 28 Nov 2016 17:20:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cBUHa-0004ZX-0m for emacs-orgmode@gnu.org; Mon, 28 Nov 2016 17:20:19 -0500 Received: from mail-vk0-x234.google.com ([2607:f8b0:400c:c05::234]:33860) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cBUHZ-0004ZB-Qg for emacs-orgmode@gnu.org; Mon, 28 Nov 2016 17:20:17 -0500 Received: by mail-vk0-x234.google.com with SMTP id x186so81891291vkd.1 for ; Mon, 28 Nov 2016 14:20:17 -0800 (PST) In-Reply-To: <87r35wf47l.fsf@nicolasgoaziou.fr> 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 , cmena@pobox.com, emacs-orgmode On 11/28/16, Nicolas Goaziou wrote: > It shows first repeat. I assume you tested that yesterday, so you got > the repeat for today. Since the repeat didn't trigger "today" (which is > actually yesterday), it also displays a reminder for the scheduled item > there. thanks for the explanation. the idea is that org 9 is using the previously scheduled section as a complete list and that it did not trigger on the first day and did on the second, and show-all nil in org 9 does not refer to the scheduled section but only to the repeater instances? > It is, per 1-year old commit (3072cb28e8627066f465f1a4af85da88135d0549). i can't keep up with master, but probably commented on that thread. > I think we need a new variable, or to change this one, to have both > behaviours possible. Suggestions (and docstrings) are welcome, we can > implement them in master branch. the issues seem to be: 1] 72x vs. 2x 2] duplicate in previously scheduled vs. not 1 is critical as it affects sorting. perhaps org-agenda-repeater-previously-scheduled-counts? values could include 'from-timestamp and 'from-previous-instance. the latter is org 8. 2 is not critical. i might be able to get used to having a complete scheduled section. [dunno if previously-scheduled is a clear name. i call it "nokori" from the japanese for "remaining" merely to be unambiguous [i don't care if it's in sumerian as long as it's unambiguous] but i don't suppose that would work for most people.] i hope this can get into maint, but if not i hope i can at least carry along a patch from master to maint if it is only fixed in master. [i'd be concerned that a patch would invite merge conflicts pretty frequently. those tend to cause confusion and stress for me.] by the way there is a bug in org 9 where org-scheduled face is erroneously used instead of org-scheduled-previously.