emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christophe Schockaert <R3vLibre@citadels.eu>
To: emacs-orgmode@gnu.org
Subject: Detect parent with SCHEDULED or DEADLINE
Date: Thu, 14 Apr 2016 00:06:15 +0200	[thread overview]
Message-ID: <87bn5dupt4.fsf@artlab.createcnix.lan> (raw)

Hi fellow org-moders,


I am seeking to list all actions in "NEXT" state that are not planned
yet (scheduled, deadline or planning tag such as WEEK, MONTH, and other
well known :).

I will consider as planned an action which is in a subtree of a parent
action which is itself planned.

That's easy for tags, since I have inheritance, but according to
http://article.gmane.org/gmane.emacs.orgmode/49215, there is no
inheritance for SCHEDULED and DEADLINE properties.

So, I inspired myself from the proposed solution and I wrote the
following function, used in an agenda block :

#+BEGIN_SRC lisp
;; Function to skip scheduled or deadline
(defun r3v/skip-inherited-scheduled-or-deadline ()
  "Skip tasks that inherit from SCHEDULED or DEADLINE"
  (let ((next-headline (save-excursion (or (outline-next-heading) (point-max))))
        (inherited-scheduled (org-entry-get-with-inheritance "SCHEDULED"))
        (inherited-deadline (org-entry-get-with-inheritance "DEADLINE")))
    ;; I will consider the scheduled part if I can make it work with
    ;; deadlines first
    (if (org-not-nil inherited-deadline)
        next-headline
      nil)))

;; Extract from agenda block
    (tags "-WAITING-CANCELLED-WEEK-MONTH-SOMEDAY/NEXT"
          ((org-agenda-overriding-header "Non planned 'NEXT' actions")
           (org-agenda-skip-function 'r3v/skip-inherited-scheduled-or-deadline)
           ;; I don't think this one is needed, but in case I enabled it:
           (org-use-property-inheritance t)
           (org-agenda-todo-ignore-scheduled t)
           (org-agenda-todo-ignore-deadlines t)
           (org-agenda-todo-ignore-with-date t)
           (org-tags-match-list-sublevels t)
           (org-agenda-sorting-strategy
            '(priority-down todo-state-down effort-up category-up))))
#+END_SRC

However, it never detects a deadline, or scheduled property, *even if
assigned on the heading itself*.

I tried that on a very simple subtree :

#+BEGIN_SRC org
* TODO Parent todo
DEADLINE: <2016-04-15 ven.>
:PROPERTIES:
:ParentProp:   ValPar
:END:
** NEXT SubAction
:PROPERTIES:
:SubProp:   Val
:END:
#+END_SRC


I also tried to eval the following expression, manually from the tree :

#+BEGIN_SRC lisp
;;;;; With DEADLINE properties, the behavior acts strangely ;;;;;

(org-entry-get nil "DEADLINE")
;; As expected:
;; - On "Parent todo", returns <2016-04-15 ven.>
;; - On "SubAction", returns nil

(org-entry-get nil "DEADLINE" t)
;; As expected:
;; - On "Parent todo", returns <2016-04-15 ven.>
;; /!\ NOT expected:
;; - On "SubAction", still returns nil

(org-entry-get-with-inheritance "DEADLINE")
;; /!\ NOT expected:
;; - On "Parent todo", returns nil
;; - On "SubAction", returns nil


;;;;; With custom properties, it works as I expect it ;;;;;

(org-entry-get nil "ParentProp")
;; - On "Parent todo", returns "ValPar"
;; - On "SubAction", returns nil

(org-entry-get nil "ParentProp" t)
;; - On "Parent todo", returns "ValPar"
;; - On "SubAction", returns "ValPar"

(org-entry-get-with-inheritance "ParentProp")
;; - On "Parent todo", returns "ValPar"
;; - On "SubAction", returns "ValPar"
#+END_SRC


Globally, org-use-property-inheritance is set to nil.

I currently have Org "8.3.3-43-g0b97a5-elpaplus" from ELPA as reported.

There might also be an easier way I didn't think of to achieve what I
want (list actions not planned), but I would also like to understand
what's wrong or what should be done to make the function work.


Any help will be appreciated :)
Kind Regards,

Christophe



-- 
--------------->  mailto:R3vLibre@citadels.eu
Once it's perfectly aimed, the flying arrow goes straight to its target.
Thus, don't worry when things go right.
There will be enough time to worry about if they go wrong.
Then, it's time to fire a new arrow towards another direction.
Don't sink.  Adapt yourself !  The archer has to shoot accurately and quickly.
[Words of Erenthar, the bowman ranger] <---------------<<<<

             reply	other threads:[~2016-04-13 22:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 22:06 Christophe Schockaert [this message]
2016-04-14  3:04 ` Detect parent with SCHEDULED or DEADLINE Adam Porter
2016-04-14  4:17   ` Adam Porter
2016-04-14  7:13     ` Nicolas Goaziou
2016-04-14  7:24       ` Adam Porter
2016-04-14  7:57         ` Nicolas Goaziou
2016-04-14 21:28           ` Christophe Schockaert
2016-04-14 21:49             ` Christophe Schockaert
2016-04-14 22:46               ` Adam Porter
2016-04-14 23:11                 ` Christophe Schockaert

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=87bn5dupt4.fsf@artlab.createcnix.lan \
    --to=r3vlibre@citadels.eu \
    --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).