From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views] Date: Mon, 23 Apr 2018 23:08:50 +0200 Message-ID: <871sf5pr4t.fsf@nicolasgoaziou.fr> References: <23248.48530.817172.917300@frac.u-strasbg.fr> <87in8ricbd.fsf@nicolasgoaziou.fr> <23261.58554.814734.521862@frac.u-strasbg.fr> <87sh7m0zsd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55456) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAiho-0000tb-1G for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 17:09:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fAihj-0004Sx-27 for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 17:09:00 -0400 Received: from relay6-d.mail.gandi.net ([217.70.183.198]:59661) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fAihi-0004ST-RV for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 17:08:54 -0400 In-Reply-To: (Carsten Dominik's message of "Mon, 23 Apr 2018 18:03:15 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Carsten Dominik Cc: org-mode list , Alain.Cochard@unistra.fr Hello, Carsten Dominik writes: > I would be interested to discuss a better solution. It would be nice is > list items could be TODO's, but I though long and har about this back when, > and over allo those years, I could not think of anything that could be > implemented with reasonable effort. I think we have to make inline tasks more limited, yet still useful. One major technical drawback stems from the fact that they allow contents. *************** Foo ... *************** END It means that they allow, e.g., properties (it hurts inheritance), or clocks that do not belong to the containing headline but to the inline task itself... It would be a major pain if we had to handle this seriously, as a core feature. Now, if we allow them to have no contents, it becomes much more manageable. It means we can still have TODO, tags, priority, but no clock, no properties, no log... It would also mean we would disallow SCHEDULED and DEADLINE keywords, but we can make an exception for those, and allow a planning line right after an inline task. So, basically, there would be two forms of inline tasks: *************** Foo and *************** Foo SCHEDULED: <...> DEADLINE: <...> With this simplification, we could manage them, probably without too much hassle. If you want to associate the task some contents, you can attach, e.g., some drawer below. It is not part of the inline task syntax, yet it could work well in practice: *************** TODO Foo :task: This is because the... :end: However, there is another important drawback: they look like headlines. That breaks a fundamental assumption in Org: any line that doesn't start with an asterisk (I'm oversimplifying here) "belongs" to the first line starting with one above. This is simply not true with inline task, so we use the `org-with-limited-levels'. It kind of works, except in parts of Org that forgot to use it (lots of fun ahead). We could go further and get away from the starred syntax and the column 0. E.g., !! TODO Foo :bar:baz: The advantage is that they would integrate better with the rest of the document: - Grocery list - Apples - Bread !! REMINDER ... However, it would be a /lot/ more work to implement the feature shared with regular headlines (TODO switching, tags inheritance)... but, at least, they would look better. Regards, -- Nicolas Goaziou