emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Detect parent with SCHEDULED or DEADLINE
Date: Thu, 14 Apr 2016 02:24:32 -0500	[thread overview]
Message-ID: <87h9f48xfz.fsf@alphapapa.net> (raw)
In-Reply-To: 87r3e8zmrf.fsf@nicolasgoaziou.fr

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Actually, `org-entry-get-with-inheritance' is an internal function,
> which shouldn't be called at all. The entry point is `org-entry-get',
> which can be called with an appropriate INHERIT optional argument.

Ah, I see.  So I guess the solution to Christophe's issue is to use
this:

#+BEGIN_SRC elisp
(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 "SCHEDULED" t))
        (inherited-deadline (org-entry-get "DEADLINE" t)))
    ;; I will consider the scheduled part if I can make it work with
    ;; deadlines first
    (if (org-not-nil inherited-deadline)
        next-headline
      nil)))
#+END_SRC

At least I learned some more about Org by trying to fix it the wrong
way.  :)  Thanks, Nicolas.

  reply	other threads:[~2016-04-14  7:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 22:06 Detect parent with SCHEDULED or DEADLINE Christophe Schockaert
2016-04-14  3:04 ` Adam Porter
2016-04-14  4:17   ` Adam Porter
2016-04-14  7:13     ` Nicolas Goaziou
2016-04-14  7:24       ` Adam Porter [this message]
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=87h9f48xfz.fsf@alphapapa.net \
    --to=adam@alphapapa.net \
    --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).