From: Charles Berry <firstname.lastname@example.org>
Subject: Re: [BUG] org-confirm-babel-evaluate breaks inline src blocks
Date: Sat, 23 Nov 2013 18:24:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20131123T183305email@example.com> (raw)
Eric Schulte <schulte.eric <at> gmail.com> writes:
> Charles Berry <ccberry <at> ucsd.edu> writes:
> > Eric Schulte <schulte.eric <at> gmail.com> writes:
> >> Charles Berry <ccberry <at> ucsd.edu> writes:
> 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
Juat to be sure that I understood what was happening, I instrumented
org-babel-get-src-block-info and ran the ECM I posted at the start of this
org-babel-get-src-block-info got called twice for the first src block, then
I got prompted
"Evaluate this emacs-lisp code block on your system? "
If I answer 'n' (skip the block redefining org-confirm-babel-evaluate,
then I get prompted for the inline src block _without_
org-babel-get-src-block-info being called again.
If I answer 'y' (redefine org-confirm-babel-evaluate as a lambda form),
I get the error message.
org-babel-exp-results: Wrong type argument: integer-or-marker-p, nil
next prev parent reply other threads:[~2013-11-23 18:24 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 [this message]
2013-11-23 19:28 ` Eric Schulte
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).