emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Fletcher Charest <fletcher.charest@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Linked tasks
Date: Mon, 16 Jun 2014 17:48:03 +0200	[thread overview]
Message-ID: <CAGk6a7kiLZ-QyrXHX=edKtRrPOJ8AuZizbGp5P9efM3ZdCu6Gg@mail.gmail.com> (raw)
In-Reply-To: <87sin729a3.fsf@ericabrahamsen.net>

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Hi Eric,

Thank you, I will have a closer look at org-depend, although it seems to me
that it's more 'depend' in the sense of 'this task has to be done for this
other task to be doable'. But I only had a glimpse on the code.

Regards,

FC


On Sat, Jun 14, 2014 at 10:19 AM, Eric Abrahamsen <eric@ericabrahamsen.net>
wrote:

> Fletcher Charest <fletcher.charest@gmail.com> writes:
>
> > Dear all,
> >
> > I was wondering if there was a way to link the status of two tasks in
> > an agenda file (or even across multiple agenda files). Sometimes, a
> > single task (in my case, updating my CV) might be a useful step in
> > two different projects. If the tasks is marked DONE in one project
> > (in one subtree), I would like the other one to be marked DONE as
> > well. Is it possible or even implemented?
> >
> > Cheers,
> >
> > FC
>
> There's an org-depend package in the contrib directory that's supposed
> to do this, but I haven't looked at it before... Vanilla Org only does
> dependencies within the same subtree.
>
> E
>
>
>

[-- Attachment #2: Type: text/html, Size: 1668 bytes --]

  reply	other threads:[~2014-06-16 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14  7:43 Linked tasks Fletcher Charest
2014-06-14  8:19 ` Eric Abrahamsen
2014-06-16 15:48   ` Fletcher Charest [this message]
2014-06-25 19:57     ` Pete Ley

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='CAGk6a7kiLZ-QyrXHX=edKtRrPOJ8AuZizbGp5P9efM3ZdCu6Gg@mail.gmail.com' \
    --to=fletcher.charest@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).