From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [bug] timed repeater shows up in wrong place Date: Sun, 13 Nov 2016 18:21:46 +0100 Message-ID: <87h97bqor9.fsf@nicolasgoaziou.fr> References: <87bmxpk30w.fsf@nicolasgoaziou.fr> <87twbhim1m.fsf@nicolasgoaziou.fr> <87inrxo5yt.fsf@cmena.pobox.com> <87a8d8o0rv.fsf@cmena.pobox.com> <878tsqfhoo.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53183) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c5yTX-00063n-5M for emacs-orgmode@gnu.org; Sun, 13 Nov 2016 12:21:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c5yTT-0002DK-U2 for emacs-orgmode@gnu.org; Sun, 13 Nov 2016 12:21:51 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:43535) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c5yTT-0002DD-O1 for emacs-orgmode@gnu.org; Sun, 13 Nov 2016 12:21:47 -0500 In-Reply-To: (Samuel Wales's message of "Fri, 11 Nov 2016 12:12:46 -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: emacs-orgmode , cmena@pobox.com Hello, Samuel Wales writes: > ok, i have a new -Q minimal testcase, which is attached. it explains > how to run it at the top. > > the relevant part is at the bottom, so you could just copy that if you > prefer to try your own setup instead. it's 3 lines. > > the task is this: > > *********** NEXT xyzzy test > SCHEDULED: <2016-11-07 Mon 17:00 .+1d> > make this be a date that is before real-time today > it should show up in agenda time grid > but it does not I can reproduce it, now. > note that this time, (setq org-agenda-repeating-timestamp-show-all nil). This was the missing setting. Notwithstanding the bug, I'm not sure to understand what is your use case here. If a nil `org-agenda-repeating-timestamp-show-all' treated time-stamps with a repeater as regular time-stamp in the agenda, I could see a use for that. However, AFAIU, a nil `org-agenda-repeating-timestamp-show-all' treats a time-stamp with a repeater as its closest repeat (from today). It makes little sense, in particular with schedules or deadlines. So, what is wrong with `org-agenda-repeating-timestamp-show-all' default value? Regards, -- Nicolas Goaziou