From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id IINNCm7pxmO5UgAAbAwnHQ (envelope-from ) for ; Tue, 17 Jan 2023 19:31:10 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id CPJQCm7pxmORhQAAauVa8A (envelope-from ) for ; Tue, 17 Jan 2023 19:31:10 +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 A97B72D54B for ; Tue, 17 Jan 2023 19:31:09 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHqiq-0006Sf-0i; Tue, 17 Jan 2023 13:30:12 -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 1pHqin-0006SB-Rl for emacs-orgmode@gnu.org; Tue, 17 Jan 2023 13:30:10 -0500 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHqij-00075R-71 for emacs-orgmode@gnu.org; Tue, 17 Jan 2023 13:30:07 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 1E0A4240329 for ; Tue, 17 Jan 2023 19:30:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1673980203; bh=0WH34DNuUv4opEhXL5VEYAVz/3pC1NJt3tBvVOaSN/I=; h=From:To:Cc:Subject:Date:From; b=BlHq2Z8eYbuXU/+AkHq4jhAmGEsJD+neZ0+q7aLow+t8d7Xn2fvCFPorwcgtPuuJS owSC5ITd+diYhbgGjPaFO26IXaPE/Kt0jYjAluTtIHhIeYoRfO2YEAa3M/JfEEVPqx 8fNSsE/Fw7ZkmXSf6VLFSjAgirqo4V9YPe7Rw9x03MlKQJiLudxJY/cALOptUtsZDg QLJPxklyfEU6goJJm7EgHhjoVTkbrkkBPReOSL0r1JlpR7UfqfusyLOKQXGOQDAgNm 6H1Ox6URDpRHnIW+3n4oTnC0SdZ+45YrJFgQJr0JEqCdLeRnksHWRj2qu2rGF+sb9A LxEhE/gcvrAcg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NxHVv4Gnqz9rxN; Tue, 17 Jan 2023 19:29:59 +0100 (CET) From: Ihor Radchenko To: David Masterson Cc: Daniel Fleischer , emacs-orgmode@gnu.org Subject: Re: org-todo-keywords and task sequence In-Reply-To: References: Date: Tue, 17 Jan 2023 18:30:25 +0000 Message-ID: <87edrtggji.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1673980269; a=rsa-sha256; cv=none; b=AHH+9iYO2LU2K6qJQ9VKA36Temx5+lf1nKEhMBYkl61twx4v+iSQEn6jDTZFBM2vnR1uV4 1Q3/rXVipZtoh//69is4lUAhag/EIkN6JGPPbcciwdhlzmf5rBLK0JqBtuyA9tSnvNamaA SZNEVcTGE++IWn1Z+aMVRsuWF+1FDPxN8ppRwaV1gyStblgWHFy38V1pfMTgC+LySp4vQE 1O1lYWXM37qbs5TEbJssTocnboM4HFuJt/BQtz9reGoFjr/jYWUQ2rA7TIlBfd7WlUI8id Vuq5rtU3GwfxDbGvBHlohpU6/uNarnNZGhxTnm/bobaRBtRG3QHicOcfYJk61w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=BlHq2Z8e; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1673980269; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=/bVBugcJL6HZ2xWC/lkYAFUwOuV7fCO9Cq/xJgycTOk=; b=HVbqshcZUiVMAxK6+IwWIlu1mPKpfMiyIImDuo/klAt9J3RS+gNvQRlbp4UeO5fsl1XlOJ /8COnXLFxUcyLrdljaAaXY5e3cMoRvWkgKI3V5DNVj6Gno2tUNv56PbkLG/U8r6c+eKP1G tfy7ObmQ/hZPwsPH663z5pZ2S2VV1rttbu6YveVZbfZiao3tpZ2XxjxoTj4XfFgiMFnl3W 2/LZHeqRWQ/tQcoO7FAaX+LVEKwdDRj7tAHGNg22Rnex1dAjH7XWeLj3D3/T12FD8aLHV6 l5DafTY7KNPZj0/YJmh17By2Ybs/iBpeJ1982dyJbwxPBM0xndfEgRv4zTOs+Q== X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -7.88 X-Spam-Score: -7.88 X-Migadu-Queue-Id: A97B72D54B Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=BlHq2Z8e; dmarc=pass (policy=none) header.from=posteo.net; 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-TUID: PRmZjhAdSSec David Masterson writes: > The problem is (I think), when you attach @ or ! to the state and, as you > cycle thru (S-right), new unintended notes will be added as you cycle to > the state you're looking for. True? If you attach @ or !, those notes are not unintended. S-right is not for you to play around, it is for actual work on actual tasks. If you tell Org to take a not on switching to next TODO state, that's what you want. If you don't want it, don't put @ or !. > Can you repeat a keyword in org-todo-keywords? Perhaps there should be a > sparse table defining, for a current state, what are the potential next > states? ... No. S-right feature is there for simple workflows. I am against introducing complex workflows for no reason. It will do no good for the users. Complex workflows are rarely useful in practice, except some specialized scenarios, which are not common enough to include into the core. And yes, you can use org-edna or custom org-trigger-hook if you need something non-orthodox. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at