From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id gBx6ObRe11/ZUgAA0tVLHw (envelope-from ) for ; Mon, 14 Dec 2020 12:46:44 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id iLNINbRe118dFQAAbx9fmQ (envelope-from ) for ; Mon, 14 Dec 2020 12:46:44 +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 E61069408EF for ; Mon, 14 Dec 2020 12:46:39 +0000 (UTC) Received: from localhost ([::1]:55492 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1konFO-0002at-TB for larch@yhetil.org; Mon, 14 Dec 2020 07:46:38 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:46690) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1konEe-0002a2-0I for emacs-orgmode@gnu.org; Mon, 14 Dec 2020 07:45:52 -0500 Received: from mail-pf1-x431.google.com ([2607:f8b0:4864:20::431]:33690) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1konEc-0002ZX-6f for emacs-orgmode@gnu.org; Mon, 14 Dec 2020 07:45:51 -0500 Received: by mail-pf1-x431.google.com with SMTP id h186so1492948pfe.0 for ; Mon, 14 Dec 2020 04:45:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=+0i955RvGFnMtzicH3K0Xk6V5+Cx8p5dwd8uUK73uWQ=; b=isBl2OeOom9DSX29KnrUeHWIC0nZAhR+V9nMyn/sM3km8yvZq9aIB0/ZSaVNdK2/Jt CG1wjKKkx6w8YA2al7AfaN2fOGIEw0t3N4FjpL0E06yvPX1VYQ9HSSarg2rXjHkuuPnc 2MHy3MZFBMHaUQADYfFIOFI0JnRK/IT8cnPw8Dl7CZI0DjF7rZAZR9OH2RD/h2bBWDF/ Lhgg2cxmO2YKklMThSmK5rpiqcG3YzvVzD7mK5fptlpyzyPXTeLY1rK6XQ1SkNLA0Vwb fDBBteioRtVbbVwETMwI+XBNNUQ/SOeOedmZg8hoR7f7TfvD9qtXhWRCzuDb/UWIELZC LfAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=+0i955RvGFnMtzicH3K0Xk6V5+Cx8p5dwd8uUK73uWQ=; b=VZqQ16KfXh1tFvsSz0GJ24POgE/NYx1Br6DjGnPMkwsUIQf70l6FeabRlS9RAao/P9 tAdAuyBKwstPdKaZgpogzyRWWfDiSHTMPhqtW3KCOveGaW6ZlmLJzSvL9G3JR9XaI0Jv Tai9eRa70ede7VHPp1xOjlXq6vFUFJD0tOI210pwgxfGub2f4e34fbC3/MwCiqWu3Rk1 wnQ9C7nbfGAwcF0pa/PfEVTwxhCvcguFuryqBy3U3duR84Y2WqD7uuaCq3Xqkxokgr6O nM5G48qgrtSWmNKbOhK/sAPqy0jGbzWd62zjtiAAj+Dy0OZM/UcZgsflu4JViZSJKet9 dQyw== X-Gm-Message-State: AOAM531vzxFcpoVRENgRoHb1p3QOiPQN4RXLBQksUO4z74HXVXZiN1hf 0HY4jEXciz4g/t/o6d4zNKo= X-Google-Smtp-Source: ABdhPJzIzuSPglYWXL37+G/6N3wfwwEk8u+67+xA+5JMjk9zQJ+xbfkgmEWGNqLf/3Hh8vHzdwLbFA== X-Received: by 2002:a63:1805:: with SMTP id y5mr23850163pgl.27.1607949948553; Mon, 14 Dec 2020 04:45:48 -0800 (PST) Received: from localhost ([50.7.251.66]) by smtp.gmail.com with ESMTPSA id b13sm3789461pfi.162.2020.12.14.04.45.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 14 Dec 2020 04:45:47 -0800 (PST) From: Ihor Radchenko To: Jean Louis Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options In-Reply-To: References: <7330ab95c71d5d41d7fa6faffeaf300f@isnotmyreal.name> <20201211082501.GA18715@tuxteam.de> <871rfwctb2.fsf@localhost> <87y2i23vhr.fsf@localhost> Date: Mon, 14 Dec 2020 20:49:37 +0800 Message-ID: <877dpklfha.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::431; envelope-from=yantar92@gmail.com; helo=mail-pf1-x431.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -0.71 Authentication-Results: aspmx1.migadu.com; dkim=fail (headers rsa verify failed) header.d=gmail.com header.s=20161025 header.b=isBl2OeO; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=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-Migadu-Queue-Id: E61069408EF X-Spam-Score: -0.71 X-Migadu-Scanner: scn0.migadu.com X-TUID: qj19HouIXdt7 Jean Louis writes: > Do you mean this: > > ** DONE Objective > CLOSED: [2020-12-13 Sun 20:00] > *** TODO [#B] Step to do 1 > *** TODO Step to do 2 > > when org-enforce-todo-dependencies is true I can still say DONE for > Objective above. I have mentioned it today already. Maybe it works on > your side, it does not work here. Do I do something wrong? I am on > development Emacs version and it does not enforce under emacs -Q >> I cannot reproduce what you observe. Also, one can forcefully change >> todo state to done even when org-enforce-todo-dependencies is set to >> TRUE. To do it, C-u C-u C-u C-c C-t needs to be used instead of C-c C-t >> for setting the todo state. > > I can observe in emacs -Q from development version. > > So you say when you try to close senior heading that you cannot close > it? I can when that variable is true or nil, do you think it is bug? > > I can give you access to Emacs over remote ssh and you can try because > if it is bug, it is serious for those other thinkers but me. I just looked into this more. Most likely you were trying to set this variable manually. To take effect, this variable should be set using customisation interface, before loading org, or you may need to run M-x org-reload. > It looks like I am only one observing that. And especially me I do not > like depending on Org mode to dictate how to close items. So when > there is somebody else to join in the notion that is where feature is > appropriate. Otherwise I consider Org rather made and designed for > other way thinkers and doers, not for us who think from senior > objectives as priorities where subordinate items should become > redundant and not marked as "done". org-mode is developed mostly be enthusiasts. Some popular features are used by many different people using different workflows. Those features get a lot of attention and become quite customisable. Other features, are only used by their author and maybe a few other people who agree on the way the feature is implemented. Naturally, these less commonly used features are more biased towards their author's workflows. However, I don't see why a patch improving org-mode flexibility would not be welcome. > My personal list of for a day has 7 items currently. Not 250. Those > are rather objectives, goals and purposes. Single items under > objectives are well known actions to be done and need not be marked as > TODO, but I can. My focus is on the meaning of what has to be done and > I do not need to look into tags or properties. Your informational > emails gave me to thinking so I have implemented it all. I also find it helpful to combine the objective + a note about concrete action to take on the objective. The concrete action helps to get started on the objective without drowning myself into thinking (but not doing) about all the things I need to do on that objective. >> Note that you are also risking to complain about things that are >> actually not a problem. Simply because you don't have a need to >> investigate what is possible. > > Yes, some of those needs disappeared when I have seen so many > obstacles. I did not use some features like org-agenda because it was > in front of me what I have to do. Things were not scattered like Org > manual advises and I disadvise. It is different paradigm approach and > so for many needs I need not even investigate what is possible. I am > interested in paradigms, approaches, methods but not in general in > gluing things together which are not meant to be together. Would you mind writing a paragraph or two to improve the "5 TODO Items" section of the manual? At least, we can inform people that the ability to scatter todo items all around the documents does not mean that it has to be done. > Jean