* `:wrap src latex' now fails on export
@ 2017-12-24 20:17 Berry, Charles
2017-12-24 23:16 ` Nicolas Goaziou
0 siblings, 1 reply; 3+ messages in thread
From: Berry, Charles @ 2017-12-24 20:17 UTC (permalink / raw)
To: emacs-org-mode
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.
FWIW, changing the lang to something besides `latex' has no effect.
Chuck
p.s. Not sure when this stop working.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: `:wrap src latex' now fails on export
2017-12-24 20:17 `:wrap src latex' now fails on export Berry, Charles
@ 2017-12-24 23:16 ` Nicolas Goaziou
2017-12-25 5:58 ` Berry, Charles
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Goaziou @ 2017-12-24 23:16 UTC (permalink / raw)
To: Berry, Charles; +Cc: emacs-org-mode
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: `:wrap src latex' now fails on export
2017-12-24 23:16 ` Nicolas Goaziou
@ 2017-12-25 5:58 ` Berry, Charles
0 siblings, 0 replies; 3+ messages in thread
From: Berry, Charles @ 2017-12-25 5:58 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: emacs-org-mode
> On Dec 24, 2017, at 3:16 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> I fixed it in maint.
>
Yes, indeed. Thank you!
Chuck
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-12-25 5:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-24 20:17 `:wrap src latex' now fails on export Berry, Charles
2017-12-24 23:16 ` Nicolas Goaziou
2017-12-25 5:58 ` Berry, Charles
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).