From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views] Date: Mon, 23 Apr 2018 14:31:22 -0700 Message-ID: <87bme9obit.fsf@ericabrahamsen.net> 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> <871sf5pr4t.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60150) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAj6G-00063H-5j for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 17:34:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fAj6D-00072b-2E for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 17:34:16 -0400 Received: from [195.159.176.226] (port=35000 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fAj6C-00071b-Rw for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 17:34:13 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fAj41-0006xN-3W for emacs-orgmode@gnu.org; Mon, 23 Apr 2018 23:31:57 +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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > 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... Would there be any consideration for an inline syntax that looks more like a link? Personally, when I want inline TODOs, I want them because there's a particular chunk of text that I need to do something with. What about something that looks like: In 2005 there were approximately [[TODO: Verify this; SCHEDULED: ; :statistics:][4,500]] Confucius Institutes in operation worldwide. That's kind of made-up, but the one-line syntax seems like it would be well suited to providing tags, priority, scheduling, etc., but none of the more bulky attributes that are part of a proper headline. WDYT? Eric