From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id MNVZLbRgamOMngAAbAwnHQ (envelope-from ) for ; Tue, 08 Nov 2022 14:59:16 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id UOuSLLRgamMKjAAAG6o9tA (envelope-from ) for ; Tue, 08 Nov 2022 14:59:16 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 635C7C3C1 for ; Tue, 8 Nov 2022 14:59:16 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1osP7c-0005Ag-Mf; Tue, 08 Nov 2022 08:58:36 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1osP7a-000585-Oa for emacs-orgmode@gnu.org; Tue, 08 Nov 2022 08:58:35 -0500 Received: from whuk14.whukhost.com ([5.77.41.174]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1osP7M-0001nV-FI for emacs-orgmode@gnu.org; Tue, 08 Nov 2022 08:58:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=heagren.com ; s=default; h=Content-Transfer-Encoding:Content-Type:Message-ID:Subject:To: From:Date:MIME-Version:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=jitc7QEymFHn4goydYM1N+opRn49siVE9rr13xgGI1w=; b=f1+IBfjdVbqNfbYyWS6iOJCvVp nj7vMIOvH+/HFPI5ENck58ECtJXbaH+5bLMWxa0arvPSUQVN9G1EbERRKo4KBj/IWgdzyS7ndd3Oc 3pVQjgnpwoFhChoGgPjfiDFwu25qYBxmOQcfCmRggSJKI/Fomi7cyF+Nbk6up7SJh05D+fi7PeQLl Kii4NVru/4wCSMgoPIXUSookgIdYEn8e5bd86GyODsNREw9Eo0fzmAPUB6RSAl1GnIWUZO3Hy9Ave mIZ8qMlpdSih8CItvnco6CRj43DWjKyctX8yHpivev274kQ50ElARpZwLQV+txb346/zUOhoReubE sIxuPm7g==; Received: from [::1] (port=45868 helo=whuk14.whukhost.com) by whuk14.whukhost.com with esmtpa (Exim 4.95) (envelope-from ) id 1osP6b-005SKz-Pf for emacs-orgmode@gnu.org; Tue, 08 Nov 2022 13:57:33 +0000 MIME-Version: 1.0 Date: Tue, 08 Nov 2022 13:57:33 +0000 From: hugo@heagren.com To: emacs-orgmode@gnu.org Subject: Suggestion: refer to other scheduled tasks in DEADLINE/SCHEDULE User-Agent: Roundcube Webmail/1.5.2 Message-ID: X-Sender: hugo@heagren.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - whuk14.whukhost.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - heagren.com X-Get-Message-Sender-Via: whuk14.whukhost.com: authenticated_id: hugo@heagren.com X-Authenticated-Sender: whuk14.whukhost.com: hugo@heagren.com X-Source: X-Source-Args: X-Source-Dir: Received-SPF: pass client-ip=5.77.41.174; envelope-from=hugo@heagren.com; helo=whuk14.whukhost.com X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1667915956; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=jitc7QEymFHn4goydYM1N+opRn49siVE9rr13xgGI1w=; b=hBQekEyRyYcdM4qn6wqyasTveGU1CIGiv03Qbk4dYIughyX3Duyp5xIsv5fN7+M5gF2478 s34EyEyTCQkeI6oeWgzwWLFi1thk2PK8mn/vq+Rbbgy+xLfRHTyQgO+4prS8OlwWIdP29G qxgHQMq9irgkWxTGV6/+0iH+//L0eZrunbO93gyAgPsBSjYjrBopelFCbe7I1jC5r7SukR N/fjJh6xaj6luC2XEvFCA46c6P+kyFEBWo4+zRJ9NP8g7qELpN3C1wZsNtHmT9lemEblGp AurtegBSYvZjIHSrVKpGeJMrAhFzuui2jvm9vHB/J6wbJ1hH4vUr3gRjZ7s7TA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1667915956; a=rsa-sha256; cv=none; b=NdgcMMtYOv+d6HD0Cr2kS61YOpczgqT9A26lOMhb5dS80z+cTD7AL4+4YN4YPLahrTUhJK 7In/Tnz8xJ+GRrXSZIc1gql6dKIrCtivaALdPV7WcOTD2CQHkblHk/dWTadF2kZcrQlrbV uYLEzOMiiTE9NEDU1EU5fHG1Te9NeEIBhqQ7E02f5C0o2JTNIK7/UjPilcfd7zCIKyfZOS PIhWpyN+2UWYIHEujcCCw3Vs2yPva3D33XK1w1McANnyODNh5BAnzP3Z0AsHaPvdqPI8Tu 6AiFHLkHBKYuywEwAHFxcXdpbAhrf8DTEnwzR2ynCZqQgRCuVN3Q+ii189AsaQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=heagren.com header.s=default header.b=f1+IBfjd; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 1.19 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=heagren.com header.s=default header.b=f1+IBfjd; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 635C7C3C1 X-Spam-Score: 1.19 X-Migadu-Scanner: scn1.migadu.com X-TUID: OgflBoONKpsM Sorry if this has been asked on the list before -- I searched briefly and couldn't find anything. I use org mode for scheduling events (which are not tasks, and therefore do not have a TODO status) as well as for logging tasks (which do have a TODO status). Often, I find I want to set a deadline (less often, a schedule) for a task identical to the timestamp of an event (e.g. there's a seminar on Thursday, in time for which I need to read two papers). At the moment, I do this by looking up the event, copying the timestamp, then setting the deadline in each task to that timestamp. This is laborious, often quite fiddly, especially if the event's timestamp repeats (as with weekly seminar), but the task only relates to a specific instance of that repeat (the paper I need to read has to be read in time for /this week's/ seminar, so I have to look up the timestamp and check what the next match on the repeater will be, then input that manually). 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 `---- 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!). This would be great, but it still doesn't solve the repeater/specific date problem. For this, we would need some sort of special syntax which selects one out of the various correct dates. Perhaps: ,---- | * Important Seminar | :PROPERTIES: | :CUSTOM_ID: seminarid | :END: | <2022-10-27 Through +1w> | | * TODO Read Famous Paper | DEADLINE: :id seminarid :after <2022-11-08 Tue> | | * TODO Read Other Paper | DEADLINE: :id seminarid :after <2022-11-08 Tue> `---- (This is only a suggestion, to demonstrate that some special syntax would be necessary. I'm not wedded to the use of keys, or the specific keys I have suggested, or anything like that.) I don't have the knowledge of org, or the time at the moment to implement any of this (though I wouldn't be upset if somebody else did!). At least for now though, some questions: - What do people think of this as an idea? - What would be a good solution to the extra syntax problem? (a similar question seems to have been asked before: ) One day, I might find some time to look at the codebase and implement this if nobody else does.. thanks, Hugo