[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [bug] timed repeater shows up in wrong place
From: |
Nicolas Goaziou |
Subject: |
Re: [O] [bug] timed repeater shows up in wrong place |
Date: |
Sat, 03 Dec 2016 23:47:44 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello,
Samuel Wales <address@hidden> 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.
>> 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