emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [rfc] the meaning of org-agenda-repeating-timestamp-show-all
Date: Fri, 11 Nov 2016 16:43:35 -0700	[thread overview]
Message-ID: <CAJcAo8uLsmke1zXDMkXO3WFadjw4Xy4pDxQjL9x0jvhkahw=fQ@mail.gmail.com> (raw)

i am getting bitten by more than one apparent repeater
change in org 9.

i posted another bug with an mce.

org-agenda-repeating-timestamp-show-all docstring says:

  When nil, only one occurrence is shown, either today or
  the nearest into the future.

this is confusing to me (fog), so here is my interpretation for
confirmation [or repudiation :)] from the mailing list:

  - repeating timestamp means any of (+ ++ .+) and (event
    scheduled deadline) -- NO EXCEPTIONS
  - today means real-world today -- NO EXCEPTIONS
    1) timestamp date -- no
    2) date the agenda is showing -- no
       - this could make sense, but if you are showing an
         n-day span, which one is "today"?  even if we
         choose a definition, i presume "showing date" or similar is
         more unambiguous nomenclature than "today"
    3) real-world today -- yes
  - future means future from real-world today -- NO EXCEPTIONS
    1) future from timestamp -- no
    2) future from date the agenda is showing -- no
       - this could make sense, but ...
    3) future from real-world today -- yes

consequence: if you are showing real-world today and
tomorrow as a 2 day span (first showing date =
real-world today), and it would not repeat today, but would
repeat tomorrow, it will show tomorrow.  if it would repeat
today, it will show on today's date in the agenda, today.

this is not always the case in org 9, but something like it seems to
be the case in org 8.  i can provide an mce.


p.s.  if any changes are made, i propose to have a variable for
debugging purposes.  it would contain the date that agenda thinks is
real-world today.  thus, a test case could work both real-world today
and tomorrow.

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  And
ANYBODY can get it.

Denmark: free Karina Hansen NOW.
  UPDATE 2016-10: home, but not fully free

             reply	other threads:[~2016-11-11 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 23:43 Samuel Wales [this message]
2016-11-11 23:52 ` [rfc] the meaning of org-agenda-repeating-timestamp-show-all 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='CAJcAo8uLsmke1zXDMkXO3WFadjw4Xy4pDxQjL9x0jvhkahw=fQ@mail.gmail.com' \
    --to=samologist@gmail.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).