From: Jiajian Huang <ispinfx@gmail.com>
To: Jiajian Huang <ispinfx@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: Can't not export source block [9.0.1 (9.0.1-elpa @ /Users/user/.emacs.d/elpa/org-20161118/)]
Date: Mon, 12 Dec 2016 08:03:47 +0800 [thread overview]
Message-ID: <CAMWOVx=ON7Xx+Gc_JZG9-Osc_dkoBctAC3S-xFm2xy==DjbtWQ@mail.gmail.com> (raw)
In-Reply-To: <87fulub166.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Thanks for you reply. Reinstalling does not help until I follow
http://emacs.stackexchange.com/questions/28441/org-mode-9-unable-to-eval-code-blocks
, remove all *.elc in the org directory and byte-compile all again.
Best regards,
Ivan
On Mon, Dec 12, 2016 at 5:34 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Jiajian Huang <ispinfx@gmail.com> writes:
>
> > After update to org 9.0, the source code block can't no longer be
> exported
> > and
> > org alerts an error.
> >
> > The minimal config I use is
> >
> > (package-initialize)
> >
> > (setq debug-on-error t
> > debug-on-signal nil
> > debug-on-quit nil)
> >
> > (require 'org)
> >
> > where the org is installed by elpa.
> >
> > The test.org file contains
> >
> > #+BEGIN_SRC latex :results drawer :exports results
> > \begin{eqnarray}
> > a + b = c \label{eq1}
> > \end{eqnarray}
> > #+END_SRC
> >
> > ONLY. Running C-c C-e l l gives error
> >
> > Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>
> I cannot reproduce it. I suspected an installation that went wrong. You
> could try to remove Org completely and install it again.
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 2028 bytes --]
prev parent reply other threads:[~2016-12-12 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 3:48 Bug: Can't not export source block [9.0.1 (9.0.1-elpa @ /Users/user/.emacs.d/elpa/org-20161118/)] Jiajian Huang
2016-12-11 21:34 ` Nicolas Goaziou
2016-12-12 0:03 ` Jiajian Huang [this message]
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='CAMWOVx=ON7Xx+Gc_JZG9-Osc_dkoBctAC3S-xFm2xy==DjbtWQ@mail.gmail.com' \
--to=ispinfx@gmail.com \
--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.