From: "Carlos García" <carloscg@gmail.com>
To: ccberry@ucsd.edu
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] src_blocks - :wrap blocks not being overwritten
Date: Wed, 31 Oct 2018 10:26:12 +0100 [thread overview]
Message-ID: <CAKzqKV2x3D2kYOyFUY1FQVf+72PLyWLJvAxD4Q5=JvMN9bnv4w@mail.gmail.com> (raw)
In-Reply-To: <B5DD9C8A-5055-4124-B82A-21F64B4B1E63@ucsd.edu>
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]
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' than can be nicely customized.
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.
Regards,
Carlos
On Tue, Oct 30, 2018 at 4:24 PM Berry, Charles <ccberry@ucsd.edu> wrote:
>
>
> > On Oct 30, 2018, at 3:35 AM, Carlos García <carloscg@gmail.com> 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.
>
>
> > That way, the needed change would be rather elegant:
> >
> > :line 2478 of ob-core.el:
> > | ;; Possible results types.
> > | '(drawer example-block export-block fixed-width item
> > | plain-list src-block table wrap-block)
> >
> > What would the repercussions be if `special-block' is added to the list?
> >
>
> Few, I think. But except for those special-blocks that have defined
> actions they would be ignored upon export.
>
> the `results' special-block would be ignored, IIUC.
>
> I suspect what you want is a `drawer', which encloses results without
> further consequences that example blocks or export blocks impose.
>
> HTH,
>
> Chuck
>
>
>
[-- Attachment #2: Type: text/html, Size: 2934 bytes --]
next prev parent reply other threads:[~2018-10-31 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 21:29 [BUG] src_blocks - :wrap blocks not being overwritten Carlos García
2018-10-29 16:00 ` Berry, Charles
2018-10-30 10:35 ` Carlos García
2018-10-30 15:24 ` Berry, Charles
2018-10-31 9:26 ` Carlos García [this message]
2018-10-31 16:24 ` Berry, Charles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKzqKV2x3D2kYOyFUY1FQVf+72PLyWLJvAxD4Q5=JvMN9bnv4w@mail.gmail.com' \
--to=carloscg@gmail.com \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).