Re: Is the cascading logic of outlines a feature, or a design bug?

[Samuel Wales]

inline tasks are arguably a limited implementation of the other model
and have had issues where they didn't work well with one feature or
another of org, so much so that i got into the habit of not using
them.  thus, modulo parsers, inline tasks might be used as a very
rough lower bound of the havoc a full implementation might wreak,
including on 3rd party tools and user code?  dunno.  just an idea.


On 12/27/22, Max Nikulin <manikulin@gmail.com> wrote:
> On 27/12/2022 00:03, abq@bitrot.link wrote:
>> When I searched prior to posting, the only info I could find was how to
>> work around the restriction. But my question isn't how to work around
>> it; my question is, what is its purpose?
>
> I have an impression that I saw messages explaining that the real
> problem is to implement the feature consistently and to avoid too much
> code for handling it in various functions. I do not have specific links.
> Reading such discussion I would pay more attention to messages from
> Carsten, Bastien, Nicolas.
>
>> It doesn't affect regexp search efficiency.
>
> Regexps would be more complex, sometimes several iterations would be
> required. You may underestimate amount of code that should be adapted
> for this feature.
>
> In general, I do not mind to have such feature e.g. to have an overview
> headings with comments between deep dive notes. However if I desperately
> need it, I will write a custom unfolding function (for tagged
> subheadings or for drawers). I am unsure that benefits outweigh
> additional complexity and performance penalty.
>
> This topic belongs to a several feature requests that pop up regularly
> and fade with almost no outcome (intra-word emphasis, merged cells in
> tables).
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com