From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: BUG: agenda for current days excludes reoccurring events
Date: Sat, 28 Jan 2017 23:26:50 +0200 [thread overview]
Message-ID: <87o9yqyixx.fsf@iki.fi> (raw)
In-Reply-To: 877f5frqy2.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Jarmo Hurri <jarmo.hurri@iki.fi> writes:
>
>> In particular the fact that you see it for all other days except today
>> makes absolutely no sense, right?
>
> It does make sense, but probably not when there is no TODO keyword.
> Also, your sentence is inaccurate: you see it _once_ in the past, not
> every others day.
That is correct, only once in the past, my bad. (Which explains some of
the weirdness in my own, more complicated setup.) Still not sure why it
would be appropriate for a TODO _as a default_ (not to show it for
today, but for future days), but like I said: we're operating above my
pay grade. Just _trying_ to provide some answers to your questions, not
sure if this is helping.
>>> I think that a nil `org-agenda-prefer-last-repeat' should display :
>>> - only the base date when the entry has a TODO keyword; - every
>>> repeat between base date and today, inclusive, otherwise.
>>>
>>> It also applies to SCHEDULED and DEADLINE repeaters.
>>>
>>> Behaviour with a non-nil value needs not be changed.
>>>
>>> WDYT?
>>
>> This is slightly beyond my pay grade, but I hope a nil
>> 'org-agenda-prefer-last-repeat' would also display all repeats for
>> _future_ days.
>
> This is orthogonal to the issue. There's a dedicated variable for
> that: `org-agenda-show-future-repeats'.
If I am on the right track here, org-agenda-show-future-repeats controls
future repetitions, and org-agenda-prefer-last-repeat controls
repetitions for today? Is that correct? (Feel completely free to ignore
this if I am on the wrong track.) I am not sure how this would work for
timed events, since "today" and "future" are not mutually exclusive:
part of today is still in the future.
> If no one objects, I'll just implement the behaviour quoted above.
Sounds like the best option to me. I can try give better informed
comments after I see what the effect will be in my setup.
Jarmo
next prev parent reply other threads:[~2017-01-28 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 8:01 BUG: agenda for current days excludes reoccurring events Jarmo Hurri
2017-01-28 14:15 ` Nicolas Goaziou
2017-01-28 15:25 ` Jarmo Hurri
2017-01-28 18:15 ` Nicolas Goaziou
2017-01-28 21:26 ` Jarmo Hurri [this message]
2017-02-21 18:27 ` Nicolas Goaziou
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=87o9yqyixx.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--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).