From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: agenda for current days excludes reoccurring events
Date: Sat, 28 Jan 2017 15:15:08 +0100 [thread overview]
Message-ID: <87o9yrs237.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k29fbol7.fsf@iki.fi> (Jarmo Hurri's message of "Sat, 28 Jan 2017 10:01:08 +0200")
Hello,
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
> - bug: day agenda for current day does not show reoccurring events
>
> - how to replicate with the ECM provided
> 1. untar the file provided below
> 2. cd into created dir
> 3. edit the first line of file agenda-setup.el so that the latest org
> release lisp is in the load path
> 4. run
> emacs -q --load agenda-setup.el
> 5. run command (org-agenda)
> 6. press 'a' for day agenda
> 7. press 'b' and/or 'f' to move backwards and forward in time
>
> - how the bug shows up: the reoccurring meeting will show up yesterday
> and in upcoming days, but not in the current day
This is the consequence of `org-agenda-prefer-last-repeat' default
value.
However, this behaviour doesn't make much sense when the entry is not
a task (i.e., it hasn't any TODO keyword). In this case,
`org-auto-repeat-maybe' doesn't apply, and the base date is never moved
forward in time.
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?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-01-28 14:15 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 [this message]
2017-01-28 15:25 ` Jarmo Hurri
2017-01-28 18:15 ` Nicolas Goaziou
2017-01-28 21:26 ` Jarmo Hurri
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=87o9yrs237.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
/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).