emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Brian van den Broek <brian.van.den.broek@gmail.com>
Cc: emacs-orgmode@gnu.org, Fabrizio Chiarello <fabrizio.chiarello@ieee.org>
Subject: Re: View inherited DEADLINEs in agenda
Date: Wed, 9 Nov 2011 09:10:57 +0100	[thread overview]
Message-ID: <A341EB4D-21F5-4B04-A3DE-75FFE43CE56D@gmail.com> (raw)
In-Reply-To: <CAF6DajK3aMU1MziX=S0Bq6mQD4FveEP-3q4WLfrFJw7a-FwyGw@mail.gmail.com>


On 8.11.2011, at 23:35, Brian van den Broek wrote:

> On 7 November 2011 16:29, Carsten Dominik <carsten.dominik@gmail.com> wrote:
>> 
>> On Nov 7, 2011, at 1:19 PM, Giovanni Ridolfi wrote:
>> 
>>> Fabrizio Chiarello <fabrizio.chiarello@ieee.org> writes:
>>> 
>>> 
>>>> I have many tasks with a DEADLINE, and I wish to have their subtasks to
>>>> inherit such DEADLINE. To this aim, I set:
>>>> 
>>>>  (setq org-use-property-inheritance (quote ("DEADLINE")))
>>>> 
>>> 
>>>> The problem is that the agenda only shows deadlines for the tasks that
>>>> define them
>>> 
>>> is DEADLINE  a property that can be inherited?
>> 
>> Deadlines can currently *not* be inherited.  I would probably advice
>> against implementing this because of performance issues that would
>> result for the construction of the agenda.
>> 
>> - Carsten
> 
> 
> Hi all,
> 
> Here's a thought: what about a function which scans a subtree of an
> item that has a deadline and adds that same deadline to any
> descendants that lack a deadline? It seems to me that this would, via
> a one time user intervention, meet the OP's need, without the constant
> overhead  about which Carsten is concerned.

This is a good idea and very easy to do.
The only disadvantage is that any new entries you make
would not get the deadline.  Though, I think, one
could put a function into org-insert-heading-hook
to check for a deadline higher up in the tree and copy it.

- Carsten

> 
> It further occurred to me that invoked without arguments, it would
> prompt the user for each item without deadline, with a prefix
> argument, apply all the deadlines automatically, and, with a numeric
> prefix n, automatically apply the alterations n-levels down.
> 
> Best,
> 
> Brian vdB

  reply	other threads:[~2011-11-09  8:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 12:03 View inherited DEADLINEs in agenda Fabrizio Chiarello
2011-11-07 12:19 ` Giovanni Ridolfi
2011-11-07 12:22   ` suvayu ali
2011-11-07 13:16     ` Fabrizio Chiarello
2011-11-07 13:23       ` Gustav Wikström
2011-11-07 14:29   ` Carsten Dominik
2011-11-07 19:46     ` Fabrizio Chiarello
2011-11-08 22:35     ` Brian van den Broek
2011-11-09  8:10       ` Carsten Dominik [this message]
2011-11-14 13:38         ` Fabrizio Chiarello
2012-04-03  7:16           ` Bastien
2012-04-11 13:38             ` Vedang

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=A341EB4D-21F5-4B04-A3DE-75FFE43CE56D@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=brian.van.den.broek@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fabrizio.chiarello@ieee.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).