From: Ihor Radchenko <yantar92@posteo.net>
To: hugo@heagren.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Suggestion: refer to other scheduled tasks in DEADLINE/SCHEDULE
Date: Wed, 09 Nov 2022 04:46:30 +0000 [thread overview]
Message-ID: <87educbuqh.fsf@localhost> (raw)
In-Reply-To: <b21797bf4a3dc9baf71030f66995f6fb@heagren.com>
hugo@heagren.com writes:
> I think it would be great if other org headlines could be referenced in
> DEADLINEs and SCHEDULEs. This would effectively solve my problem: I
> could just add an id (or whatever identifier the implementation ends up
> using) to the event headline, and then use that id in the DEADLINE or
> SCHEDULE, thus:
>
> ,----
> | * Important Seminar
> | :PROPERTIES:
> | :CUSTOM_ID: seminarid
> | :END:
> | <2022-10-27 Through +1w>
> |
> | * TODO Read Famous Paper
> | DEADLINE: seminarid
> |
> | * TODO Read Other Paper
> | DEADLINE: seminarid
> `----
Note that the above is ambiguous: The event may have multiple
timestamps, and it is unclear which one to select in general case.
> Then the tasks to read papers will show up in my agenda with deadlines
> when the seminar starts. As far as I know, there isn't a way to do this
> already (though if there is, I would be happy to use it!).
You can use diary-style timestamps like
DEADLINE: <%%(my/copy-date :id "seminarid" :after "2022-11-08 Tue")>
where `my/copy-date' is an arbitrary Elisp function that is executed in
Diary environment, with `date' and `entry' variables being set at
runtime. See `org-class' for a sample implementation.
Since `my/copy-date' can be anything, you can implement any logic you
need.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-11-09 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 13:57 Suggestion: refer to other scheduled tasks in DEADLINE/SCHEDULE hugo
2022-11-09 4:46 ` Ihor Radchenko [this message]
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=87educbuqh.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=hugo@heagren.com \
/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).