From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id LPIIEoHWw19VPQAA0tVLHw (envelope-from ) for ; Sun, 29 Nov 2020 17:12:33 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id qKFODYHWw1/vDQAAB5/wlQ (envelope-from ) for ; Sun, 29 Nov 2020 17:12:33 +0000 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 D9BE5940481 for ; Sun, 29 Nov 2020 17:12:32 +0000 (UTC) Received: from localhost ([::1]:45272 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kjQFT-0007QO-Rc for larch@yhetil.org; Sun, 29 Nov 2020 12:12:31 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:44260) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kjQF7-0007Pw-78 for emacs-orgmode@gnu.org; Sun, 29 Nov 2020 12:12:09 -0500 Received: from static.rcdrun.com ([95.85.24.50]:42847) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kjQF5-000538-L5 for emacs-orgmode@gnu.org; Sun, 29 Nov 2020 12:12:09 -0500 Received: from localhost ([::ffff:197.157.0.29]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C000B.000000005FC3D665.00001AA6; Sun, 29 Nov 2020 17:12:04 +0000 Date: Sun, 29 Nov 2020 20:11:58 +0300 From: Jean Louis To: Tim Cross Subject: Re: Adding Org Files to org-agenda-files Message-ID: References: <87r1od181i.fsf@gmail.com> <87h7p9135u.fsf@gmail.com> <87sg8tymeb.fsf@gmail.com> <87k0u4zupw.fsf@gmail.com> <87ft4s5oug.fsf@localhost> <87360sz5ap.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <87360sz5ap.fsf@gmail.com> User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-Spam_score_int: 29 X-Spam_score: 2.9 X-Spam_bar: ++ X-Spam_report: (2.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_PASS=-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.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: daniela-spit@gmx.it, emacs-orgmode@gnu.org, Ihor Radchenko Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -1.78 X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-TUID: B55r37VcQO8O * Tim Cross [2020-11-29 16:01]: > >> If the type of heading is "task" then I do not need to use "TODO" as > >> it implies it is task. But Org headings do not have fixed types so it > >> is visually and practically better to use TODO. Here would the > >> inheritance be useful more than to tags. As if user marks one heading > >> as TODO, then all subtrees could automatically get its TODO. > > > > This assumes the only things you have under a TODO heading is other TODO > headings. That isn't how I structure my work. I might have many other > headings under a TODO heading which are not tasks, but are perhaps > related to the task. Sometimes I might have many tasks which are not > dependent on each other and so are all at the same level. That is amazing and true how you say. One heading may have many other non-TODO related headings which should not inherit the tag. When I was writing about htat I was thinking on database backed tasks. Every node has its "type" and if type is "Action/TODO" then such could inherit TODO tag to be visible. But if node is WWW, Note, or other type of hyperdocument, then not. For me that would be only visual tag, something in red color or similar or highlighted stuff because the hyperdocument in the system already has "Action type" assigned. Node or heading is already TODO internally. It is very trivial on a press of a key to get all lines highlighted which are TODO. Other assignments from a parent can make more sense, for example if task is assigned to group of 3 people then such designation could be inherited or invoked to be inherited. If there are other designations such as person connected, assigned, etc. all those may be inherited in a subtree or invoked explicitly to be inherited. This spares user not to type so much and curate tasks.