[headers were somehow set to other than the mailing list itself.
maybe a gmane bug?]
On 4/20/13, Nicolas Goaziou wrote:
> I will slowly integrate org-element-at-point in core interactive
> functions, like visibility cycling. Though, fontification will have to
> wait, because the parser isn't read
On Fri, Apr 19, 2013 at 5:27 PM, Nicolas Goaziou wrote:
>
>
> Hello,
>
> "Sebastien Vauban"
> writes:
>
>> Now that ":results drawer" has been introduced, I wonder why we still have
>> ":results raw".
>>
>> As once stated in this ML:
>>
>> The sole purpose of raw results is to allow insert
Hello,
"Sebastien Vauban"
writes:
> The fact that the following output a normally behaving headline[1], AFAICS.
>
> #+begin_src sh :results drawer :exports both
> echo "* Unescaped headline"
> #+end_src
>
> #+results:
> :RESULTS:
> * Unescaped headline
> :END:
>
> Though, effectively, when exp
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> Now that ":results drawer" has been introduced, I wonder why we still have
>> ":results raw".
>>
>> As once stated in this ML:
>>
>> The sole purpose of raw results is to allow inserting an headline (I
>> mean a real
Hello,
"Sebastien Vauban"
writes:
> Now that ":results drawer" has been introduced, I wonder why we still have
> ":results raw".
>
> As once stated in this ML:
>
> The sole purpose of raw results is to allow inserting an headline (I mean
> a real headline, not comma protected) in the
Hello,
Now that ":results drawer" has been introduced, I wonder why we still have
":results raw".
As once stated in this ML:
The sole purpose of raw results is to allow inserting an headline (I mean
a real headline, not comma protected) in the buffer, because headlines
cannot be c
