From: Eric Schulte <schulte.eric@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-confirm-babel-evaluate breaks inline src blocks
Date: Sat, 23 Nov 2013 09:19:07 -0700 [thread overview]
Message-ID: <87y54ff5ma.fsf@gmail.com> (raw)
In-Reply-To: loom.20131123T045908-673@post.gmane.org
Charles Berry <ccberry@ucsd.edu> writes:
> Eric Schulte <schulte.eric <at> gmail.com> writes:
>
>>
>> Charles Berry <ccberry <at> ucsd.edu> writes:
>>
> [snip]
>>
>> Thanks for pointing this out, I've just pushed up a fix.
>>
>
> AFAICS, it is still broken.
>
> I did a git pull, downloaded the patches, applied them, compiled
> ob-core.el. I am still getting
>
> org-babel-exp-results: Wrong type argument: integer-or-marker-p, nil
>
>
> I suspect that
>
> (,head (nth 6 ,info))
> ...
> (goto-char ,head)
>
> in the org-babel-check-confirm-evaluate macro is the source of the message.
>
> (nth 6 info) is nil for inline src blocks.
>
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))))
Best,
>
> HTH,
>
> Chuck
>
>
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2013-11-23 16:26 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 [this message]
2013-11-23 18:24 ` Charles Berry
2013-11-23 19:28 ` Eric Schulte
2013-11-23 20:38 ` Charles Berry
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y54ff5ma.fsf@gmail.com \
--to=schulte.eric@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.