emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: documentation request for timestamps
Date: Fri, 8 Nov 2013 13:47:14 -0700	[thread overview]
Message-ID: <CAJcAo8tPX_P5=LGFR2-LD8vmHb=y-S4ASu5UtccZzDCXmRhS3g@mail.gmail.com> (raw)

I do not know how these are intended to behave and tests are showing
inconsistent results.

It might help if these explained whether timestamp, ts, and tsia up
and down refer to untagged timestamps only, or all timestamps
including deadline, scheduled, and closed.

It might also help to explain which are the missing ones, such as
closed up and down, any active regardless of whether tagged up and
down, etc.  Are those intended to be implemented or must they be done
in user code?

It might also help to explain what happens to repeaters.  I am getting
extremely strange results.  Most recently, an untagged active
timestamp showed up with scheduled above and below, as if it had been
scheduled.

Here is the existing documentation:

===
timestamp-up       Sort by any timestamp, early first
timestamp-down     Sort by any timestamp, late first
scheduled-up       Sort by scheduled timestamp, early first
scheduled-down     Sort by scheduled timestamp, late first
deadline-up        Sort by deadline timestamp, early first
deadline-down      Sort by deadline timestamp, late first
ts-up              Sort by active timestamp, early first
ts-down            Sort by active timestamp, late first
tsia-up            Sort by inactive timestamp, early first
tsia-down          Sort by inactive timestamp, late first
===

I ask because I am trying to get this result for today:

         ;; i want this after time-up:
         ;;   untagged inactive down
         ;;   closed down
         ;;   untagged active down
         ;;     including repeater if repeats today
         ;;   deadline down
         ;;     including repeater if repeats today
         ;;   scheduled down
         ;;     including repeater if repeats today
         ;;
         ;; all repeater types (.+ ++ +) should be extrapolated
         ;; to today and show if they repeat today.  However, they should
         ;; not show tomorrow if they also repeat tomorrow.
         ;;
         ;; the extrapolated most recent repeater value should be
         ;; used in scheduled and deadline sorting.

Thanks.

Samuel

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

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

Denmark: free Karina Hansen NOW.

                 reply	other threads:[~2013-11-08 20:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJcAo8tPX_P5=LGFR2-LD8vmHb=y-S4ASu5UtccZzDCXmRhS3g@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

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).