From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Hoffmann, Jobst" <J.Hoffmann@fh-aachen.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Export to LaTeX buffer
Date: Mon, 12 Mar 2018 15:13:46 +0100 [thread overview]
Message-ID: <87muzdcrfp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1520860336.2694.24.camel@fh-aachen.de> (Jobst Hoffmann's message of "Mon, 12 Mar 2018 13:12:18 +0000")
Hello,
"Hoffmann, Jobst" <J.Hoffmann@fh-aachen.de> writes:
> The org-mode manual version Release 9.1.6 (release 9.1.6-567-gbb5e79)
> says on page 159, that export of an org file to a LaTeX buffer is doneby C-c C-e l L.
>
> This ends in a message
>
> "Autoloading failed to define function turn-on-orgstruct"
>
> A little bit of googling tells me, that "[O] [ANN] OrgStruct is dead.
> Long live Orgalist."
>
> So I can't go on with my usual work flow, but what should I do instead?
> Do I have to write an elisp function, which opens the file generated by
> C-c C-e l l and deletes all the document stuff surrounding the contents?
> I'm interested only in the bare (LaTeX-prepared) content, because I
> continue processing the the contents in my own environment.
This looks like a mixed installation. "turn-on-orgstruct" does not exist
in master branch, which you seem to be using.
I suggest making sure you properly load Org from the git repository
instead of some other location.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-03-12 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 13:12 Export to LaTeX buffer Hoffmann, Jobst
2018-03-12 14:13 ` Nicolas Goaziou [this message]
2018-03-12 21:00 ` Samuel Wales
[not found] ` <1520882537.2694.42.camel@fh-aachen.de>
[not found] ` <87zi3d9ijs.fsf@nicolasgoaziou.fr>
2018-03-13 15:29 ` Hoffmann, Jobst
2018-03-14 13:57 ` Nicolas Goaziou
2018-03-16 18:29 ` Hoffmann, Jobst
2018-06-08 10:22 ` Export to LaTeX buffer (solved) Hoffmann, Jobst
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=87muzdcrfp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=J.Hoffmann@fh-aachen.de \
--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).