From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Berry, Charles" <ccberry@ucsd.edu>
Cc: emacs-org-mode <emacs-orgmode@gnu.org>
Subject: Re: `:wrap src latex' now fails on export
Date: Mon, 25 Dec 2017 00:16:17 +0100 [thread overview]
Message-ID: <87shbzg1j2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <5F660A3B-F655-48E2-8FDC-AAA5CF811681@ucsd.edu> (Charles Berry's message of "Sun, 24 Dec 2017 20:17:17 +0000")
Hello,
"Berry, Charles" <ccberry@ucsd.edu> writes:
> I can execute this src block with no problems:
>
> #+begin_src emacs-lisp :wrap src latex :exports results
> "some-text"
> #+end_src
>
>
> and it will produce the expected result:
>
> #+RESULTS:
>
> #+begin_src latex
> some-text
> #+end_src
>
> and if I then export as (say) `C-c C-e C-b l L n y', I get just `some-text' in the LaTeX buffer.
>
> But if I try to execute the first block, i.e. `C-c C-e C-b l L y'
> I get an error *before* the prompt for the latex src block appears and
> this in my *Message* buffer :
>
> ,----
> | org-babel-exp process emacs-lisp at position 3...
> | Evaluate this emacs-lisp code block on your system? (y or n) y
> | executing Emacs-Lisp code block...
> | Code block evaluation complete.
> | org-babel-exp process latex at position 14...
> | org-babel-exp-process-buffer: Wrong type argument: integer-or-marker-p, nil
> `----
>
> I've tried edebug-ing and got as far as `org-babel-exp--at-source',
> but haven't been able get any further.
Your initial block generates a new source block, that the export process
has to evaluate. Unfortunately, Org assumes all source blocks to be
evaluated are located within the original buffer. Since it can find the
newly generated one, it returns an error.
I fixed it in maint.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-12-24 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 20:17 `:wrap src latex' now fails on export Berry, Charles
2017-12-24 23:16 ` Nicolas Goaziou [this message]
2017-12-25 5:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shbzg1j2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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.