From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, cmena@pobox.com
Subject: Re: [bug] timed repeater shows up in wrong place
Date: Mon, 14 Nov 2016 00:32:58 +0100 [thread overview]
Message-ID: <878tsnq7kl.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8sRCMz=cRzNZ7+Rn3rBAnBrM2QcCFPNwb21fOMEQZBZNA@mail.gmail.com> (Samuel Wales's message of "Sun, 13 Nov 2016 12:38:21 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> On 11/13/16, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> If a nil `org-agenda-repeating-timestamp-show-all' treated time-stamps
>> with a repeater as regular time-stamp in the agenda, I could see a use
>> for that.
>
> not sure what you mean by this.
I mean that a variable ignoring all repeaters in agenda is useful. It
means that, e.g.,
<2016-11-13 Sun +1d>
is seen as
<2016-11-13 Sun>
To put it differently, this would ignore repeaters until the task is
marked as done, which is repeaters original purpose.
However `org-agenda-repeating-timestamp-show-all' seems to do something
different.
>> However, AFAIU, a nil `org-agenda-repeating-timestamp-show-all' treats
>> a time-stamp with a repeater as its closest repeat (from today). It
>
> which means today, right? in org 9, this has changed.
It doesn't mean necessarily today. Let's assume today is <2016-11-13 Sun>.
Now, consider, e.g.,
<2016-11-09 Wed +3d>
Closest repeat in the future is <2016-11-15 Tue +3d>, which is neither
today nor tomorrow.
AFAIU, a nil `org-agenda-repeating-timestamp-show-all' means that
nothing will appear on <2016-11-09 Wed>, but the task will be displayed
on <2016-11-15 Tue>, as if it was automatically marked as done without
my consent. Odd.
Note that I could understand the use for that. But there is worse:
<2016-11-09 Wed .+3d>
In this case, I cannot possibly guess when the next repeat is going to
show, since it depends on the date at which the task is done. As
a consequence, treating the above as <2016-11-09 Wed +3d> is just plain
wrong IMO. Every repeat displayed in the agenda could be inaccurate.
>> makes little sense, in particular with schedules or deadlines.
>
> i don't get why.
Because schedules and deadlines are already repeated, somehow, in the
agenda. Today being <2016-11-13 Sun>, let's consider a task, not done
yet, with the following SCHEDULED time:
<2016-11-09 Wed +1d>
I will get "Sched.4x". Yet closest repeat is today, so a nil
`org-agenda-repeating-timestamp-show-all' dumbly displays the task
without the "Sched.4x".
I lost the information the task started 4 days ago. If I mark it as
done, it still appears on today, without any feedback telling me it is
a new task that started 3 days ago, this time.
Why would I want that?
>> So, what is wrong with `org-agenda-repeating-timestamp-show-all' default
>> value?
>
> t you mean? if i am showing today and tomorrow, or the whole week, i
> don't want to see the repeater show up on every day.
OK, if you mainly use "+1d" repeaters, it can be a bit verbose. But then
again, if `org-agenda-repeating-timestamp-show-all' ignored the repeat
altogether, it wouldn't fill up the agenda.
> i just want it to show up today. then i doneify it, and then i just
> want it to show up tomorrow. this is org 8 behavior for me.
Again, if `org-agenda-repeating-timestamp-show-all' ignored the repeat
part, you would still have this with schedules and deadlines, as
exhibited above.
The only difference would be with plain time-stamps (no SCHEDULED nor
DEADLINE keyword). In Org 8,
<2016-11-09 Wed +1d>
appears today, no matter what "today" means for the agenda. Ignoring the
repeater would not make it appear today unless today is <2016-11-09 Wed>,
of course.
> not sure we're communicating accurately though.
It is difficult to communicate since the subject is not very well
defined.
In a nutshell, I fail to see any use for this variable for schedules and
deadlines (except, perhaps, in the future part of the agenda). I also
fail to see any use for it in conjunction with ".+" and "++" repeaters.
I can be wrong, but I'd like to understand where.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-11-13 23:33 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 [this message]
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
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=878tsnq7kl.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=cmena@pobox.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).