From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 0D/LKRJ46GR4CwEASxT56A (envelope-from ) for ; Fri, 25 Aug 2023 11:44:50 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id +EamKRJ46GT15gAAauVa8A (envelope-from ) for ; Fri, 25 Aug 2023 11:44:50 +0200 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 4A2203507C for ; Fri, 25 Aug 2023 11:44:50 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Cs2b3Xm3; 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"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1692956690; 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=XSCjJK6mGvvBrBmhA+4I8Ld2WUwOQOLDU/h1PGUaJ5M=; b=uVqQMfo+i1jUWZouyFzs0I4HznRh4gBwMnU6GlAf2GD6bHnHt8MfPfpHz9Sz4lLMhUU3sb 6wwYaQBPSs0WXz4OZjO8r+OyfGtUm3VOOm+49yWuT2bCPK8FOavJgH+s0wRLWACIjnWtNC m/31QiQUykTYsD1rm+1Y5PkOO23lUh0ddpy9x+U1r5X2zk83sQZvtek1Dlw+i9EeC55sUE KgmWsYPdkBAWWXpDfj/SXsAMd48ulBzmEhvo/+/4oJAaJAaHz8Dn23r0x1auXtzqsd+xWO MzqN+zBLdsE5x2bMOyeSmUEP9w/AYL18+4ENiwe/qfIMHW0lCES1IoInzdQPgQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Cs2b3Xm3; 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"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1692956690; a=rsa-sha256; cv=none; b=i64+YeRERLyO5HAPQs2+XHt2c0fzxxbi0llE7TtdL+h0Aoo4pa57vYtEjEaBpbd9YJQsGc niTnHqTqxD9AIewnm0venOpQ4xajJPb7W6Qm/wGkrpGEUxXAeAIphh7LxuN5jZDGyuG8Vh vi1bMPrqcyaqJUgOj5dyuJy2dc2S+ojmz2ixeUhC+tvQFzU2bj6Ogn4jkAHrSWpULwNcEi c8Wl0Dx2aupHb7et4l68dh9+hNYKu2VWDcAiJhjdg6VnBbDWZY5aPaKricQs4gXR+sSYGk nziFYFkFhFWRLN3szoYNAWFM95x1a5k4kOoKQxiDTXWnFi0TM+ut+vIEuvaEvw== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qZTMH-00089i-I5; Fri, 25 Aug 2023 05:44:01 -0400 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 1qZTMF-00089E-1I for emacs-orgmode@gnu.org; Fri, 25 Aug 2023 05:43:59 -0400 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 1qZTMB-0005Pk-Uw for emacs-orgmode@gnu.org; Fri, 25 Aug 2023 05:43:58 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id B20A1240106 for ; Fri, 25 Aug 2023 11:43:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1692956633; bh=cu+s5l8BitKFuOutjPjhVVjhE+YiNV8luBFdqMXE61A=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Cs2b3Xm3IoitRPc8uDwgya1wD0z1eh/p+lJN+Ao+Nz+fGI2j/34fFhi+UyuzTP2ww XMpnSKwPqb3Qd/msPerq61U5oGP91ICvcqFfZN6fJG2c0RhiWa71cXg6b/nSmP/P3E cA4g9/GHewi6uxQ4qm0tv9k/GiJa4hbHhqx/BpdrV2F7IDjAddMgJ26W+moXCU3jUV l+KeeQq9NXryGRsO5oiXAhwXjCGTgh0hOXmIOABW612CNKhoUG8djUodN0yMrX3zYw PMZF4IFazmwp6BnyIhiBlZ9qnKvdqjL5nmq9udq+aGrI2rSVZnUBi4LVKqqbTId0Pc deP1CrnAeY9oA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RXFQJ74wSz6tx7; Fri, 25 Aug 2023 11:43:52 +0200 (CEST) From: Ihor Radchenko To: Bastien Guerry Cc: "Fraga, Eric" , Samuel Wales , Max Nikulin , "emacs-orgmode@gnu.org" Subject: [DISCUSSION] Re-design of inlinetasks (was: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?) In-Reply-To: <87il94wn1t.fsf@bzg.fr> References: <87o7omg4ie.fsf@alphaville.usersys.redhat.com> <87bkfip3mo.fsf@gnu.org> <87r0odrkbp.fsf@localhost> <875y5pvf04.fsf@bzg.fr> <87bkfdud55.fsf@localhost> <87cyzswhqn.fsf@bzg.fr> <875y5hn4mt.fsf@ucl.ac.uk> <878ra32jn9.fsf@bzg.fr> <87sf8a6r2l.fsf@localhost> <87v8d47jqh.fsf@bzg.fr> <87sf88d5r6.fsf@localhost> <87jztkve0g.fsf@bzg.fr> <874jko3ad6.fsf@localhost> <87a5ugk46o.fsf@bzg.fr> <87msygk3zh.fsf@localhost> <87bkewip2u.fsf@bzg.fr> <87il94k3a6.fsf@localhost> <875y54d24d.fsf@bzg.fr> <874jkok1eg.fsf@localhost> <87il94wn1t.fsf@bzg.fr> Date: Fri, 25 Aug 2023 09:44:23 +0000 Message-ID: <87fs47h2x4.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_H5=0.001, RCVD_IN_MSPIKE_WL=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 X-Migadu-Scanner: mx2.migadu.com X-Migadu-Spam-Score: -6.43 X-Spam-Score: -6.43 X-Migadu-Queue-Id: 4A2203507C X-TUID: cA3SavLvBseW Bastien Guerry writes: > I suggest removing the support for inline tasks *as they are designed > today*, yes. What I have in mind is slightly different: Keep inlinetasks for now and implement a better alternative, which we can hopefully come up with in this discussion. Later, promote the alternative, slowly deprecating the current inlinetask implementation. Eventually, remove inlinetask code from Org in favour of the new alternative. > ... I suggest reassessing the real problem we are trying to > solve here, and see if we can come up with an approach that does not > complexify Org's core syntax too much. > E.g. perhaps allowing a :noheadingexport: tag to prevent the export of > a heading would fit 90% of what is expected from inline tasks in the > example you gave. >... Again, if the core feature is > to prevent some headings from being exported, then other approaches > can be explored. May you elaborate? Is it something similar to :ignore: tag from ox-extra contributed package? If so, it is not what the use-cases I have in mind are about: 1. Inlinetasks should be exported as "boxes" - something similar to margin or inline notes - Can be used as a memo TODO in draft publication printout - As Samuel suggested, inlinetasks could be a basis of review comments - like what GDocs/Office provides in margin "chat" 2. When folding, I expect inlinetasks to behave like drawers/blocks - not hiding the continuation text below. >> Yup. That's why I think that we need to make inlinetasks have distinct >> syntax. > > I'm reluctant to supercharge Org's core syntax for this feature. > I may be wrong, but I'd love to see if inline tasks are widely used, > and if so, for what specific purpose. I understand and tend to agree that it would be best to avoid extending Org syntax too much. Generally, the two points I listed above can be accomplished if we use ordinary headings with a special tag. However, I am also not fully sold on such idea. It would be nice if inlinetasks would not require adding many stars in front, even in deeply nested subtrees. What about another popular request - people often want to turn plain lists into a kind of headings? We might introduce a new list type ** TODO this is a list, serving just like inlinetask :tag1:tag2: :PROPERTIES: <...> :END: *1. DONE numbered list The idea is that one just needs two stars " **" to create such list - very convenient and in line with the proper heading syntax. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at