Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use org-latex-export-to-latex instead of org-export-as-latex when exporting via emacs #57

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

kassick
Copy link

@kassick kassick commented Apr 24, 2013

No description provided.

@hsitz
Copy link
Owner

hsitz commented Apr 24, 2013

kasik --

Thanks for these changes. I wasn't aware of any problems. I haven't kept
up with with org-mode much, but I notice that recent Org 8.0 has
significant changes in export and the export dispatcher. At the moment I
don't have Emacs installed on any of my machines, so I'm wondering:

(1) were these changes necessary to make latex and pdf export work with Org
8.0, and

(2) do latex and pdf export still work fine with these changes on pre-8.0
Org?

I guess basically I'm asking if these 'org-latex-export....' commands exist
previous to Org 8.0.

Also, seems like I'd also need to change the 'd' choice of 'export to pdf
and automatically open pdf viewer' .

Thanks,

Herb

On Wed, Apr 24, 2013 at 9:25 AM, kassick [email protected] wrote:


You can merge this Pull Request by running

git pull https://github.com/kassick/VimOrganizer master

Or view, comment on, or merge it at:

#57
Commit Summary

  • Fix problem with export-as-latex emacs command

File Changes

Patch Links:

@kassick
Copy link
Author

kassick commented Apr 24, 2013

Hello,
I'm a complete emacs noob (have kept the hell away from it for the past 15 years) and I've just recently been introduced to orgmode, so I'm not all that sure of what I'm doing ;)
I've got org 8.0.1 from ELPA (org-20130422). Haven't tested yet with some earlier version of orgmode; shall test it soon.
The ``export-as-latex´´ command gives me the following error with org-8.0.1:

ERROR: Symbol's value as variable is void: org-export-latex-default-packages-alist

Going though http://orgmode.org/Changes_old.html I guess I could still use the original command if I had set the variable to nil and granted all the packages I needed were in the .org file header.

But indeed, if the commands do not exist in older orgmode versions, they should be controlled by some variable, maybe set in vimorganizer initialization after asking emacs what's the version of org (can emacs do it?).

There is no org-latex-export-to-pdf-and-open , I'm not sure yet how to implement the 'd' option yet.

@hsitz
Copy link
Owner

hsitz commented Apr 24, 2013

On Wed, Apr 24, 2013 at 10:05 AM, kassick [email protected] wrote:

I've got org 8.0.1 from ELPA (org-20130422). Haven't tested yet with some
earlier version of orgmode; shall test it soon.
The ``export-as-latex´´ command gives me the following error with
org-8.0.1:

ERROR: Symbol's value as variable is void:
org-export-latex-default-packages-alist
Going though http://orgmode.org/Changes_old.html I guess I could still
use the original command if I had set the variable to nil and granted all
the packages I needed were in the .org file header.

But indeed, if the commands do not exist in older orgmode versions, they
should be controlled by some variable, maybe set in vimorganizer
initialization after asking emacs what's the version of org (can emacs do
it?).

There is no org-latex-export-to-pdf-and-open , I'm not sure yet how to
implement the 'd' option yet.

kassick -- I just noticed a few days ago that Org 8.0 was out and had some
major changes. I had wondered whether it might break something in the
VimOrganizer interface but hadn't checked into it yet. I'll get 8.0
installed and try to get any issues I find sorted out this week.

Thanks for bringing this to my attention.

-- Herb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants