From: Young-whan <youngsong15@gmail.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Latex Preview Fragment is not working on org 9.0.3 from elpa
Date: Fri, 20 Jan 2017 10:58:07 -0800 [thread overview]
Message-ID: <CADDrvYiOd4L7U0jjQ8+nVmH0vJ6m1Xf1s6qM5z-H0v-E03A8+g@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1701181253070.652@charles-berrys-macbook.local>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Looks like it is a bug? Why it is not loaded automatically while 8.2 has no
issue?
On Wed, Jan 18, 2017 at 12:56 PM, Charles C. Berry <ccberry@ucsd.edu> wrote:
> On Wed, 18 Jan 2017, Young-whan wrote:
>
> I've installed the emacs-app via port, and there was no problem with Latex
>> Preview Fragment in a buffer at all.
>>
>> Now, using the M-x package-list-packages, I've installed the latest org
>> 9.0.3, then the latex preview is not working at all.
>>
>> It comes with following error:
>>
>> org-create-formula--latex-header: Symbol’s function definition is void:
>> org-export-get-backendError during redisplay: (eval (mode-line-mode-name))
>> signaled (void-function mode-line-mode-name)
>>
>
> That is because `org-export-get-backend' is not loaded (nor autoloaded).
>
> You can type C-c C-e q to force loading of the org-export-* functions. Or
> put (require 'ox) in your init file.
>
> I don't see why `org-export-get-backend' is lacking an autoload directive.
>
> Bug??
>
> Chuck
>
[-- Attachment #2: Type: text/html, Size: 1519 bytes --]
next prev parent reply other threads:[~2017-01-20 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 19:02 Latex Preview Fragment is not working on org 9.0.3 from elpa Young-whan
2017-01-18 20:56 ` Charles C. Berry
2017-01-20 18:58 ` Young-whan [this message]
2017-01-21 10:59 ` Nicolas Goaziou
2017-01-22 16:21 ` Young-whan
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADDrvYiOd4L7U0jjQ8+nVmH0vJ6m1Xf1s6qM5z-H0v-E03A8+g@mail.gmail.com \
--to=youngsong15@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 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).