From: Samuel Wales <samologist@gmail.com>
To: Samuel Wales <samologist@gmail.com>,
cmena@pobox.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [bug] timed repeater shows up in wrong place
Date: Mon, 28 Nov 2016 15:20:15 -0700 [thread overview]
Message-ID: <CAJcAo8uPYpMPOW8SWt+jR7Oe7U8DKNy0=va+pRFdT19-o+rVYw@mail.gmail.com> (raw)
In-Reply-To: <87r35wf47l.fsf@nicolasgoaziou.fr>
On 11/28/16, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> It shows first repeat. I assume you tested that yesterday, so you got
> the repeat for today. Since the repeat didn't trigger "today" (which is
> actually yesterday), it also displays a reminder for the scheduled item
> there.
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?
> It is, per 1-year old commit (3072cb28e8627066f465f1a4af85da88135d0549).
i can't keep up with master, but probably commented on that thread.
> 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 hope this can get into maint, but if not i hope i can at least carry
along a patch from master to maint if it is only fixed in master.
[i'd be concerned that a patch would invite merge conflicts pretty
frequently. those tend to cause confusion and stress for me.]
by the way there is a bug in org 9 where org-scheduled face is
erroneously used instead of org-scheduled-previously.
next prev parent reply other threads:[~2016-11-28 22:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 22:44 [bug] timed repeater shows up in wrong place Samuel Wales
2016-11-08 22:41 ` Nicolas Goaziou
2016-11-08 23:13 ` Samuel Wales
2016-11-08 23:33 ` Nicolas Goaziou
2016-11-09 0:43 ` Samuel Wales
[not found] ` <87inrxo5yt.fsf@cmena.pobox.com>
2016-11-09 18:44 ` Samuel Wales
[not found] ` <87a8d8o0rv.fsf@cmena.pobox.com>
2016-11-09 21:52 ` Samuel Wales
[not found] ` <877f8cnsea.fsf@cmena.pobox.com>
2016-11-09 23:35 ` Samuel Wales
[not found] ` <87k2cbpito.fsf@cmena.pobox.com>
2016-11-10 18:15 ` Samuel Wales
2016-11-10 19:48 ` cesar mena
2016-11-11 10:13 ` Nicolas Goaziou
2016-11-11 19:12 ` Samuel Wales
2016-11-13 17:21 ` Nicolas Goaziou
2016-11-13 19:38 ` Samuel Wales
2016-11-13 23:32 ` Nicolas Goaziou
2016-11-16 19:26 ` Samuel Wales
2016-11-25 0:57 ` Nicolas Goaziou
2016-11-25 1:07 ` Samuel Wales
2016-11-25 7:40 ` Nicolas Goaziou
2016-11-25 22:09 ` Samuel Wales
2016-11-26 10:38 ` Nicolas Goaziou
2016-11-27 2:19 ` Samuel Wales
2016-11-27 11:15 ` Nicolas Goaziou
2016-11-27 18:59 ` Samuel Wales
2016-11-28 0:39 ` Nicolas Goaziou
2016-11-28 3:22 ` Samuel Wales
2016-11-28 7:34 ` Nicolas Goaziou
2016-11-28 22:20 ` Samuel Wales [this message]
2016-11-28 22:44 ` Samuel Wales
2016-12-02 21:44 ` cesar mena
2016-12-02 22:26 ` Nicolas Goaziou
2016-12-02 23:08 ` cesar mena
2016-12-02 23:55 ` Samuel Wales
2016-12-03 22:47 ` Nicolas Goaziou
2016-12-04 0:31 ` cesar mena
2016-12-04 8:56 ` Nicolas Goaziou
2016-12-04 12:46 ` cesar mena
2016-12-04 21:27 ` Samuel Wales
2016-12-06 11:46 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2016-11-28 13:28 cesar mena
2016-11-28 22:32 ` Samuel Wales
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8uPYpMPOW8SWt+jR7Oe7U8DKNy0=va+pRFdT19-o+rVYw@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=cmena@pobox.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).