From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: [bug] timed repeater shows up in wrong place Date: Sun, 27 Nov 2016 20:22:44 -0700 Message-ID: References: <87twbhim1m.fsf@nicolasgoaziou.fr> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37357) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBCWm-00079j-50 for emacs-orgmode@gnu.org; Sun, 27 Nov 2016 22:22:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cBCWl-0005dy-7d for emacs-orgmode@gnu.org; Sun, 27 Nov 2016 22:22:48 -0500 Received: from mail-ua0-x22d.google.com ([2607:f8b0:400c:c08::22d]:35126) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cBCWl-0005dq-2m for emacs-orgmode@gnu.org; Sun, 27 Nov 2016 22:22:47 -0500 Received: by mail-ua0-x22d.google.com with SMTP id 12so130154500uas.2 for ; Sun, 27 Nov 2016 19:22:46 -0800 (PST) In-Reply-To: <87vav8fnes.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/27/16, Nicolas Goaziou wrote: > I pushed a few more fixed in plain time-stamps and deadlines. Please > report if you find anything suspicious. please try this: SCHEDULED: <2016-09-17 Sat .+2d> emacs -Q, with a 2-day span and show-all nil. in org 8: 1] it shows today 2] it shows 2x which is perfect for my use case. in org 9: 1] it shows on both days 2] it shows 72x re 1, dunno if this was intended? re 2, org 9 is trying to do its counting from the original timestamp date. i can understand the reasoning here, but do not want it for my use case. 72x gets buried. it's a sudden pop up then a sudden drop off. i want a gradual bubbling down like in org 8. a .+30d repeater should show today, then tomorrow it should show 2x, then the next day it should show 3x. org 8 is nicer for showing the fact that 2d ago you were reminded to do it, and maybe did it but did not doneify or maybe were not able to do it. it bubbles down slowly.