Re: [O] [BUG] Inconsistency in src block hiding

[Eric Schulte]

Nicolas Goaziou <address@hidden> writes:

> Hello,
>
> Eric Schulte <address@hidden> writes:
>
>> Thanks for taking the time to collect these changes into a patch,
>> however I believe the changes you describe present /new/ behavior (e.g.,
>> new export semantics for drawers), rather than a bug repair.
>
> I'd rather say that its intent is to fix an old bug: incomplete
> specifications of drawers. Also, I don't add export semantics for
> drawers: I remove any, by default.
>

I apologize if I come across as argumentative, but I disagree with the
statement above.  The tag-line to the "Drawers" section in the manual is
"Tucking stuff away" which I think is often how drawers are used.
Changing the default drawer export behavior from "don't export" to "do
export" would be surprising, would break many existing work flows, and
would likely make drawers less useful.

In general I think the Org-mode specification is best defined by how
Org-mode is used and how it may be more easily and intuitively used in
the future.  Org-mode doesn't currently have a formal specification, and
I think that is a good thing.  Formal specification don't prevent bugs,
they just move them from the code to the spec.

Incidentally this is also why I consider the loss of result folding to
be a regression because it breaks existing usage patterns.

>
> Again, drawers allow to fold any part of an Org buffer without adding
> semantics to its contents. It's a more general solution than
> keywords. But you already know that.
>
>> For the time being I am going to bring back results folding until an
>> acceptable alternative can be agreed upon and implemented.
>
> There is already an acceptable alternative. I sincerely hope that
> reverting this won't make it impossible to be implemented later.
>

There is no rule against reverting a revision :), so we could always do
that if there is a consensus on list.

To my mind a better path moving forward would be to change the behavior
of the :RESULTS: drawer so that it is exported but *not* to change the
default drawer export behavior.  This way with a :wrap header argument
the code block results could be hidden with tab but would still be
exported.

   PRO: allows hiding code block results with tab, makes it clear where
        results begin and end, uses drawers for hiding which is what
        they are designed for, avoids the potential for hiding anything
        with a name

   CON: more syntactic weight around results, changes the existing
        default behavior, makes the "RESULTS" drawer a special type of
        drawer

There is likely a better option but this is the best that comes to mind.
Personally I am also content with the current behavior in which anything
under a #+name: may be hidden.

Cheers,

>
>
> Regards,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/