From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Shlomi Vaknin <shlomivaknin@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: Bug: Exception when trying to export inlined-code [8.3.4 (8.3.4-9-gfda14f-elpa @ ~/.emacs.d/elpa/org-20160307/)]
Date: Thu, 10 Mar 2016 10:21:19 +0100 [thread overview]
Message-ID: <87y49qlmcw.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CANyzh=gr-b+Jtyj9_F7S0XVFa=rxTqxZ4x6Q+kyf3wv1608xng@mail.gmail.com> (Shlomi Vaknin's message of "Wed, 9 Mar 2016 21:45:38 -0800")
Hello,
Shlomi Vaknin <shlomivaknin@gmail.com> writes:
> I managed to make another non-working example (should I make
> a gif showing what I see?):
>
> ---------------------------------------
> - src_elisp{3} {{{results(=3=)}}}
>
> * B
> - src_elisp{3} {{{results(=3=)}}}
> -
> -
> -
> - src_elisp{3} {{{results(=3=)}}}
> - src_elisp{2} {{{results(=2=)}}}
> - {{{results(=2=)}}}
> ---------------------------------------
>
> again, removing any line from this makes export work again. Otherwise I get
> =org-element--current-element: Wrong type argument: integer-or-marker-p,
> nil=
I cannot reproduce the problem. Could you send a complete backtrace with
un-compiled Org?
Also, could you try setting `org-element-use-cache' to nil?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-03-10 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 21:27 Bug: Exception when trying to export inlined-code [8.3.4 (8.3.4-9-gfda14f-elpa @ ~/.emacs.d/elpa/org-20160307/)] Shlomi Vaknin
2016-03-10 3:00 ` Charles C. Berry
2016-03-10 5:45 ` Shlomi Vaknin
2016-03-10 6:33 ` Bill Burdick
2016-03-10 9:21 ` Nicolas Goaziou [this message]
2016-03-11 21:13 ` Shlomi Vaknin
2016-03-13 17:34 ` Nicolas Goaziou
2016-03-13 19:34 ` Shlomi Vaknin
2016-03-13 19:45 ` Nicolas Goaziou
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=87y49qlmcw.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=shlomivaknin@gmail.com \
/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.