Ihor Radchenko writes: > In other words, it is not the section itself, but other > headline/inlinetask features, like todo keywords, tags, planning. Right?
No, it is the section itself (or the concept of "section", with its toys in Org, of course) that is important to me in this case. I am not emphasizing so much how or in which way an element can be exported, but what (semantic) role that element plays in the logical structure of an Org document. To get a little philosophical, the Org document (where I work and write) would be the idea, and the export to any format a possible concrete realization. I mean, I find it comfortable and productive to view an Org document as agnostic of any format. This use of inlinetasks that I'm discussing here occurred to me a long time ago because if I stop to think about an untitled, detached section of the level hierarchy, this Org element is a perfect candidate. It is true that you can use a special block, or another element (org is very versatile, and supports role swapping between elements), but if I have to think of a logical candidate, inlinetasks are the closest to that concept. If inlinetasks didn't exist, I'd probably use special blocks for that purpose. When I'm writing inside Org I'm not thinking about the export (at least not simultaneously), that is, about the format; I think more of the structure of the document, as something abstract. -- Juan Manuel Macías https://juanmanuelmacias.com https://lunotipia.juanmanuelmacias.com https://gnutas.juanmanuelmacias.com
