From: Eric Schulte <firstname.lastname@example.org>
To: Charles Berry <email@example.com>
Subject: Re: [BUG] org-confirm-babel-evaluate breaks inline src blocks
Date: Sat, 23 Nov 2013 12:28:31 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <loom.20131123T183305email@example.com> (Charles Berry's message of "Sat, 23 Nov 2013 18:24:17 +0000 (UTC)")
>> Indeed the fix was to set this element of info to point to the front of
>> the inline src block. I imagine that you probably don't have the
>> patched version of the relevant function loaded. Please try M-x
>> describe-function on org-babel-get-src-block-info, then jump to the
>> definition of said function where you should see the following code
>> which now sets the location of the inline src block head into the last
>> element of the info list.
>> ;; inline source block
>> (when (org-babel-get-inline-src-block-matches)
>> (setq head (match-beginning 0))
>> (setq info (org-babel-parse-inline-src-block-match))))
> That _is_ what I had loaded, but ...
> org-babel-get-src-block-info is *not* *called* for inline src blocks.
> org-babel-exp-non-block-elements doesn't call org-babel-get-src-block-info.
> Instead, it has this
> (let* ((info (org-babel-parse-inline-src-block-match))
> for inline src blocks.
> So changing org-babel-get-src-block-infodoes not fix the inline src block
Oh, I was testing with interactive evaluation, not export. I've just
pushed up another fix which should fix this for export too.
next prev parent reply other threads:[~2013-11-23 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 20:05 [BUG] org-confirm-babel-evaluate breaks inline src blocks Charles Berry
2013-11-22 15:29 ` Eric Schulte
2013-11-23 4:50 ` Charles Berry
2013-11-23 16:19 ` Eric Schulte
2013-11-23 18:24 ` Charles Berry
2013-11-23 19:28 ` Eric Schulte [this message]
2013-11-23 20:38 ` Charles Berry
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).