From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [bug] timed repeater shows up in wrong place Date: Mon, 14 Nov 2016 00:32:58 +0100 Message-ID: <878tsnq7kl.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> <87h97bqor9.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46137) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c64Gi-00008J-QY for emacs-orgmode@gnu.org; Sun, 13 Nov 2016 18:33:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c64Gh-0008Is-N1 for emacs-orgmode@gnu.org; Sun, 13 Nov 2016 18:33:00 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:57073) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c64Gh-0008Ia-Gi for emacs-orgmode@gnu.org; Sun, 13 Nov 2016 18:32:59 -0500 In-Reply-To: (Samuel Wales's message of "Sun, 13 Nov 2016 12:38:21 -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: > On 11/13/16, Nicolas Goaziou wrote: >> 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. > > not sure what you mean by this. I mean that a variable ignoring all repeaters in agenda is useful. It means that, e.g., <2016-11-13 Sun +1d> is seen as <2016-11-13 Sun> To put it differently, this would ignore repeaters until the task is marked as done, which is repeaters original purpose. However `org-agenda-repeating-timestamp-show-all' seems to do something different. >> However, AFAIU, a nil `org-agenda-repeating-timestamp-show-all' treats >> a time-stamp with a repeater as its closest repeat (from today). It > > which means today, right? in org 9, this has changed. It doesn't mean necessarily today. Let's assume today is <2016-11-13 Sun>. Now, consider, e.g., <2016-11-09 Wed +3d> Closest repeat in the future is <2016-11-15 Tue +3d>, which is neither today nor tomorrow. AFAIU, a nil `org-agenda-repeating-timestamp-show-all' means that nothing will appear on <2016-11-09 Wed>, but the task will be displayed on <2016-11-15 Tue>, as if it was automatically marked as done without my consent. Odd. Note that I could understand the use for that. But there is worse: <2016-11-09 Wed .+3d> In this case, I cannot possibly guess when the next repeat is going to show, since it depends on the date at which the task is done. As a consequence, treating the above as <2016-11-09 Wed +3d> is just plain wrong IMO. Every repeat displayed in the agenda could be inaccurate. >> makes little sense, in particular with schedules or deadlines. > > i don't get why. Because schedules and deadlines are already repeated, somehow, in the agenda. Today being <2016-11-13 Sun>, let's consider a task, not done yet, with the following SCHEDULED time: <2016-11-09 Wed +1d> I will get "Sched.4x". Yet closest repeat is today, so a nil `org-agenda-repeating-timestamp-show-all' dumbly displays the task without the "Sched.4x". I lost the information the task started 4 days ago. If I mark it as done, it still appears on today, without any feedback telling me it is a new task that started 3 days ago, this time. Why would I want that? >> So, what is wrong with `org-agenda-repeating-timestamp-show-all' default >> value? > > t you mean? if i am showing today and tomorrow, or the whole week, i > don't want to see the repeater show up on every day. OK, if you mainly use "+1d" repeaters, it can be a bit verbose. But then again, if `org-agenda-repeating-timestamp-show-all' ignored the repeat altogether, it wouldn't fill up the agenda. > i just want it to show up today. then i doneify it, and then i just > want it to show up tomorrow. this is org 8 behavior for me. Again, if `org-agenda-repeating-timestamp-show-all' ignored the repeat part, you would still have this with schedules and deadlines, as exhibited above. The only difference would be with plain time-stamps (no SCHEDULED nor DEADLINE keyword). In Org 8, <2016-11-09 Wed +1d> appears today, no matter what "today" means for the agenda. Ignoring the repeater would not make it appear today unless today is <2016-11-09 Wed>, of course. > not sure we're communicating accurately though. It is difficult to communicate since the subject is not very well defined. In a nutshell, I fail to see any use for this variable for schedules and deadlines (except, perhaps, in the future part of the agenda). I also fail to see any use for it in conjunction with ".+" and "++" repeaters. I can be wrong, but I'd like to understand where. Regards, -- Nicolas Goaziou