From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: documentation request for timestamps Date: Fri, 8 Nov 2013 13:47:14 -0700 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49222) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vet1P-0002xK-QX for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 15:52:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VesxX-0002aI-Tl for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 15:51:15 -0500 Received: from mail-wg0-x229.google.com ([2a00:1450:400c:c00::229]:54881) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VesxX-0002a8-Mj for emacs-orgmode@gnu.org; Fri, 08 Nov 2013 15:47:15 -0500 Received: by mail-wg0-f41.google.com with SMTP id b13so208650wgh.0 for ; Fri, 08 Nov 2013 12:47:14 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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.