> On Oct 31, 2018, at 2:26 AM, Carlos García wrote:
>
> The bigger issue is that it "used to work". A few releases ago, wrapped
> results could be correctly replaced when using ":results replace". I was
> wondering if the change was intentional or a side-effect of something else.
>
This com
Hi Chuck,
The `drawer' option is enough to "wrap" results, but it fails to provide
the customizability that `special-blocks' offer.
For example, `special-blocks' can be iterated with `org-element-map'. From
the point of view of theming, wrapped results use faces, such as
`org-block-begin-line' tha
> On Oct 30, 2018, at 3:35 AM, Carlos García wrote:
>
> Hi Chuck,
>
> Thanks for looking into this. How difficult/desirable would it be to create
> another block such as "wrap-block" for those blocks created with ":wrap"?
A `special-block' is a syntactic element. A `wrap-block' is not.
> T
Hi Chuck,
Thanks for looking into this. How difficult/desirable would it be to create
another block such as "wrap-block" for those blocks created with ":wrap"?
That way, the needed change would be rather elegant:
:line 2478 of ob-core.el:
| ;; Possible results types.
| '(drawer example-block
> On Oct 24, 2018, at 2:29 PM, Carlos García wrote:
>
> Hi List,
>
> The functionality of replacing blocks using ":wrap" seems to be broken.
> In this email [1] from 2014, a user reported that this was working:
>
> ,
> | * A
> |
> | #+header: :results raw replace :wrap
> | #+begin_src em
Hi List,
The functionality of replacing blocks using ":wrap" seems to be broken.
In this email [1] from 2014, a user reported that this was working:
,
| * A
|
| #+header: :results raw replace :wrap
| #+begin_src emacs-lisp
| (+ 2 2)
| #+end_src
|
| #+results:
| #+BEGIN_RESULTS
| 4
| #+END_R
