From mboxrd@z Thu Jan 1 00:00:00 1970 From: cesar mena Subject: Re: [bug] timed repeater shows up in wrong place Date: Sat, 03 Dec 2016 19:31:48 -0500 Message-ID: <87k2bgilfv.fsf@cmena.pobox.com> References: <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> <87wpfgbpf3.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60207) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cDKii-0003pk-Nn for emacs-orgmode@gnu.org; Sat, 03 Dec 2016 19:31:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cDKif-0007hx-ID for emacs-orgmode@gnu.org; Sat, 03 Dec 2016 19:31:56 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:52153) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cDKif-0007hR-Ds for emacs-orgmode@gnu.org; Sat, 03 Dec 2016 19:31:53 -0500 In-Reply-To: <87wpfgbpf3.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: Nicolas Goaziou , Samuel Wales Cc: emacs-orgmode hello, Nicolas Goaziou writes: > Hello, > > Samuel Wales writes: > >> 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? > > I'm not sure to understand. > > Anyway, I pushed a change to maint that should solve the "72x vs. 2x" > issue. just making sure i'm getting this. in maint, if org-agenda-repeating-timestamp-show-all is nil we get 72x. if it is non nil we get 2x. i'm in the 72x camp, so i don't need to do anything. when master comes around org-agenda-repeating-timestamp-show-all will go away. to get 72x make sure that org-agenda-prefer-last-repeat is nil (?) close? thanks. -cm >>> 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 implemented the following variables in master: > > - `org-agenda-show-future-repeats' > - `org-agenda-prefer-last-repeat' > > and removed `org-agenda-repeating-timestamp-show-all', which was > ambiguous. > > Basically, IIUC, setting `org-agenda-show-future-repeats' to nil and > `org-agenda-prefer-last-repeat' to t should reproduce exactly the > behaviour of Org 8. > > Also, the combination of the two variables above gives more flexibility. > > Feedback welcome. > > > Regards, > > -- > Nicolas Goaziou