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

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Detect parent with SCHEDULED or DEADLINE
Date: Thu, 14 Apr 2016 09:57:50 +0200	[thread overview]
Message-ID: <87mvowzkox.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87h9f48xfz.fsf@alphapapa.net> (Adam Porter's message of "Thu, 14 Apr 2016 02:24:32 -0500")

Adam Porter <adam@alphapapa.net> writes:

> 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

I don't think so. You cannot force inheritance for a special property,
which obey to its own rules. The optional argument is going to be
ignored. If the OP wants to get the SCHEDULED value of the current
headline or any of its parent, he can move up the hierarchy with
`org-up-heading-safe', calling `org-entry-get' at each stop.

Regards,

next prev parent reply	other threads:[~2016-04-14  7:55 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
2016-04-14  7:57         ` Nicolas Goaziou [this message]
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=87mvowzkox.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=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

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