Exporting text

Exporting text

[Peter Davis]

Well, I don't know how messed up my org-mode installation is, but in addition to my problems with LaTeX, even text exporting fails. When I try C-c C-e t A, I get:

Symbol's value as variable is void: org-drawers

Any clues what the problem might be?

Thanks!
-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Bastien]

Hi Peter,

Peter Davis <pfd@pfdstudio.com> writes:

> Well, I don't know how messed up my org-mode installation is, but in
> addition to my problems with LaTeX, even text exporting fails. When I
> try C-c C-e t A, I get:
>
> Symbol's value as variable is void: org-drawers
>
> Any clues what the problem might be?

You don't give us a lot to chew on :)

How did you install Org?

I suggest you install Org through git, as explained in the manual.

Don't forget to ~$ make autoloads or just ~$ make

HTH,

-- 
 Bastien

Re: Exporting text

[Peter Davis]

On Sun, Jan 26, 2014 at 11:14:28PM +0100, Bastien wrote:
> Hi Peter,
> 
> Peter Davis <pfd@pfdstudio.com> writes:
> 
> > Well, I don't know how messed up my org-mode installation is, but in
> > addition to my problems with LaTeX, even text exporting fails. When I
> > try C-c C-e t A, I get:
> >
> > Symbol's value as variable is void: org-drawers
> >
> > Any clues what the problem might be?
> 
> You don't give us a lot to chew on :)

Sorry.

> How did you install Org?

Org 7.something came with the OS X emacs 24.3.1 that I installed. In
November, I installed org 8 using git. Earlier this month, I installed
the 1/4/2014 update using the emacs package installer. I'm guessing
that last was what screwed me up.

> I suggest you install Org through git, as explained in the manual.
> 
> Don't forget to ~$ make autoloads or just ~$ make
> 

I'll try re-installing via git.

Thanks!

-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Peter Davis]

On Mon, Jan 27, 2014 at 10:05:29AM -0500, Peter Davis wrote:
> 
> > I suggest you install Org through git, as explained in the manual.
> > 
> > Don't forget to ~$ make autoloads or just ~$ make
> > 
> 
> I'll try re-installing via git.
> 

Ok, I tried making org from git, but I'm still having problems with
latex. When I start emacs, I get 

Symbol's value as variable is void: org-latex-classes

NOTE that when I try locate library, I still see the elpa location

Library is file ~/.emacs.d/elpa/org-20131118/org.elc

Though I don't know how that's even getting in the load path. It's not
in my .emacs anywhere. Something else? Is desktop saving this
out-of-date load somehow?

GNU Emacs 24.3.1
org version 8.2.5g

Thanks!
-pd



-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Peter Davis]

On Mon, Jan 27, 2014 at 11:19:09AM -0500, Peter Davis wrote:
> On Mon, Jan 27, 2014 at 10:05:29AM -0500, Peter Davis wrote:
> > 
> > > I suggest you install Org through git, as explained in the manual.
> > > 
> > > Don't forget to ~$ make autoloads or just ~$ make
> > > 
> > 
> > I'll try re-installing via git.
> > 
> 
> Ok, I tried making org from git, but I'm still having problems with
> latex. When I start emacs, I get 
> 
> Symbol's value as variable is void: org-latex-classes
> 
> NOTE that when I try locate library, I still see the elpa location

Ok, so two other changes seem to have me working again:

1) move the elpa directory out of the way, and
2) explicitly load ox-latex

Now emacs starts up without errors, and I can export to latex without
errors.

However, the latex output looks like complete rubbish ... just
headers, overlapping each other vertically.

Thanks!
-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Nick Dokos]

Peter Davis <pfd@pfdstudio.com> writes:

> On Mon, Jan 27, 2014 at 11:19:09AM -0500, Peter Davis wrote:
>> On Mon, Jan 27, 2014 at 10:05:29AM -0500, Peter Davis wrote:
>> > 
>> > > I suggest you install Org through git, as explained in the manual.
>> > > 
>> > > Don't forget to ~$ make autoloads or just ~$ make
>> > > 
>> > 
>> > I'll try re-installing via git.
>> > 
>> 
>> Ok, I tried making org from git, but I'm still having problems with
>> latex. When I start emacs, I get 
>> 
>> Symbol's value as variable is void: org-latex-classes
>> 
>> NOTE that when I try locate library, I still see the elpa location
>
> Ok, so two other changes seem to have me working again:
>
> 1) move the elpa directory out of the way, and
> 2) explicitly load ox-latex
>
> Now emacs starts up without errors, and I can export to latex without
> errors.
>
> However, the latex output looks like complete rubbish ... just
> headers, overlapping each other vertically.
>

Use a minimal .emacs, something like this (adjust path to suit your
situation):

--8<---------------cut here---------------start------------->8---
(add-to-list 'load-path "~/src/emacs/org/org-mode/lisp")

(require 'org-loaddefs)
--8<---------------cut here---------------end--------------->8---

Then  start emacs with

   emacs -q -l /path/to/minimal/.emacs

Visit an org file and try latex exporting. If that works, then
your init file is screwed up. If it doesn't, then your org-mode
installation is screwed up.

Nick

Re: Exporting text

[Peter Davis]

On Mon, Jan 27, 2014 at 12:00:52PM -0500, Nick Dokos wrote:
> 
> Use a minimal .emacs, something like this (adjust path to suit your
> situation):
> 
> --8<---------------cut here---------------start------------->8---
> (add-to-list 'load-path "~/src/emacs/org/org-mode/lisp")
> 
> (require 'org-loaddefs)
> --8<---------------cut here---------------end--------------->8---

Thanks, Nick,

I had to use this to get all the org-... stuff defined:

--8<---------------cut here---------------start------------->8---
(add-to-list 'load-path "~/src/org-mode/lisp")
(add-to-list 'load-path "~/src/org-mode/contrib/lisp")
;;(add-to-list 'load-path "~/src/emacs/org/org-mode/lisp")
(require 'org-loaddefs)
(require 'ox-latex)
(add-to-list 'org-latex-classes
          '("org-article"
             "\\documentclass{org-article}
             [NO-DEFAULT-PACKAGES]
             [PACKAGES]
             [EXTRA]"
             ("\\section{%s}" . "\\section*{%s}")
             ("\\subsection{%s}" . "\\subsection*{%s}")
             ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
             ("\\paragraph{%s}" . "\\paragraph*{%s}")
             ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
--8<---------------cut here---------------end--------------->8---


> 
> Then  start emacs with
> 
>    emacs -q -l /path/to/minimal/.emacs
> 
> Visit an org file and try latex exporting. If that works, then
> your init file is screwed up. If it doesn't, then your org-mode
> installation is screwed up.

The output is still screwed up, in what appears to be the same way.

Interestingly, the .tex file looks ok, at least from a cursory glance,
but most of its contents don't show up on the PDF. I tried compiling
it from the command line, but it didn't understand \hyperset{...} and
perhaps some other things, so I'm assuming org prepends some
definitions. 

The org file starts with:

--8<---------------cut here---------------start------------->8---
#+STARTUP: showeverything logdone
#+options: num:nil
#+OPTIONS:   H:5 num:t toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
#+LaTeX_CLASS: org-article
#+LaTeX_CLASS_OPTIONS: [article,letterpaper,times,12pt,listings-bw,microtype]
--8<---------------cut here---------------end--------------->8---

The org-article class is from:

http://orgmode.org/worg/org-contrib/babel/examples/article-class.html


Thanks,
-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Nick Dokos]

Peter Davis <pfd@pfdstudio.com> writes:

> On Mon, Jan 27, 2014 at 12:00:52PM -0500, Nick Dokos wrote:
>> 
>> Use a minimal .emacs, something like this (adjust path to suit your
>> situation):
>> 
>> --8<---------------cut here---------------start------------->8---
>> (add-to-list 'load-path "~/src/emacs/org/org-mode/lisp")
>> 
>> (require 'org-loaddefs)
>> --8<---------------cut here---------------end--------------->8---
>
> Thanks, Nick,
>
> I had to use this to get all the org-... stuff defined:
>
> (add-to-list 'load-path "~/src/org-mode/lisp")
> (add-to-list 'load-path "~/src/org-mode/contrib/lisp")
> ;;(add-to-list 'load-path "~/src/emacs/org/org-mode/lisp")
> (require 'org-loaddefs)
> (require 'ox-latex)
> (add-to-list 'org-latex-classes
>           '("org-article"
>              "\\documentclass{org-article}
>              [NO-DEFAULT-PACKAGES]
>              [PACKAGES]
>              [EXTRA]"
>              ("\\section{%s}" . "\\section*{%s}")
>              ("\\subsection{%s}" . "\\subsection*{%s}")
>              ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>              ("\\paragraph{%s}" . "\\paragraph*{%s}")
>              ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>
>
>> 
>> Then  start emacs with
>> 
>>    emacs -q -l /path/to/minimal/.emacs
>> 
>> Visit an org file and try latex exporting. If that works, then
>> your init file is screwed up. If it doesn't, then your org-mode
>> installation is screwed up.
>
> The output is still screwed up, in what appears to be the same way.
>
> Interestingly, the .tex file looks ok, at least from a cursory glance,
> but most of its contents don't show up on the PDF. I tried compiling
> it from the command line, but it didn't understand \hyperset{...} and
> perhaps some other things, so I'm assuming org prepends some
> definitions. 
>

AFAIK, the .tex file is (or should be) self-contained. Org has nothing
further to say about it. OTOH, if the org-article class uses special
sauce you may need to install additional latex packages. But before
you do that...

> The org file starts with:
>
> #+STARTUP: showeverything logdone
> #+options: num:nil
> #+OPTIONS:   H:5 num:t toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t
> #+LaTeX_CLASS: org-article
> #+LaTeX_CLASS_OPTIONS: [article,letterpaper,times,12pt,listings-bw,microtype]
>

...what happens if you replace org-article with just plain boring old
article? 

> The org-article class is from:
>
> http://orgmode.org/worg/org-contrib/babel/examples/article-class.html
>

TL;DR

It may be that the org-article class is busted. Or it may be that it
needs additional latex packages installed.

Nick

Re: Exporting text

[Peter Davis]

On Mon, Jan 27, 2014 at 01:06:53PM -0500, Nick Dokos wrote:
> 
> ...what happens if you replace org-article with just plain boring old
> article? 
> 

Yeah, that worked. Unfortunately, though, I didn't get the Times font
I was after.

Actually, Times was just going to be a stepping stone to what I really
want ... a) sans-serif headings and b) Palatino as the base font.

I'd welcome any suggestions on how to achieve those.

Thanks!
-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Nick Dokos]

Peter Davis <pfd@pfdstudio.com> writes:

> On Mon, Jan 27, 2014 at 01:06:53PM -0500, Nick Dokos wrote:
>> 
>> ...what happens if you replace org-article with just plain boring old
>> article? 
>> 
>
> Yeah, that worked. Unfortunately, though, I didn't get the Times font
> I was after.
>

The fact that it worked however says that the org-article class is
the culprit.

> Actually, Times was just going to be a stepping stone to what I really
> want ... a) sans-serif headings and b) Palatino as the base font.
>
> I'd welcome any suggestions on how to achieve those.
>

Why were you using org-article in the first place? Was it supposed to
help with the font choices? Bear in mind that I know nothing about
org-article.

So you have a choice to make: either fix org-article and continue using
it or throw it away and find some other way to do what you want.

For example, all you have to do to get Times is

#+LATEX_HEADER: \usepackage{times}

Getting finer control should also be possible using basic latex
techniques. Whether that's a "better" way to go is of course
debatable: it depends on a lot of variables.

Nick

Re: Exporting text

[Peter Davis]

On Mon, Jan 27, 2014 at 05:09:02PM -0500, Nick Dokos wrote:
> 
> Why were you using org-article in the first place? Was it supposed to
> help with the font choices? Bear in mind that I know nothing about
> org-article.

I found org-article when trying to find out how to control fonts,
etc. Basically, I have my own LaTeX template I use when
hand-constructing documents, and I was hoping to be able to use those
same settings when org creates a LaTeX document for me. I thought
org-article would give me that degree of control, but it probably
hasn't been updated since some prior version of org (based on the
variable names), and so is probably broken.

> 
> So you have a choice to make: either fix org-article and continue using
> it or throw it away and find some other way to do what you want.
> 
> For example, all you have to do to get Times is
> 
> #+LATEX_HEADER: \usepackage{times}
> 
> Getting finer control should also be possible using basic latex
> techniques. Whether that's a "better" way to go is of course
> debatable: it depends on a lot of variables.

Since most of these settings I'll want to use in *all* my documents,
putting all the parameters in each org file would be pretty
tedious. I'll keep looking for a more elegant solution. I'll be happy
to post here when I find something (that works!)

Thank you!

-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Thomas S. Dye]

Aloha Peter,

Peter Davis <pfd@pfdstudio.com> writes:

> On Mon, Jan 27, 2014 at 01:06:53PM -0500, Nick Dokos wrote:
>> 
>> ...what happens if you replace org-article with just plain boring old
>> article? 
>> 
>
> Yeah, that worked. Unfortunately, though, I didn't get the Times font
> I was after.
>
> Actually, Times was just going to be a stepping stone to what I really
> want ... a) sans-serif headings and b) Palatino as the base font.
>
> I'd welcome any suggestions on how to achieve those.

The Koma scripts for LaTeX use sans-serif headings.  Try this:

#+name: koma-article
#+header: :results silent
#+begin_src emacs-lisp
   (require 'ox-latex)
   (add-to-list 'org-latex-classes
                '("koma-article"
                  "\\documentclass{scrartcl}
                   \\usepackage{microtype}
                   \\usepackage{tgtermes}
                   \\usepackage[scale=.9]{tgheros}
                   \\usepackage{tgcursor}"
                  ("\\section{%s}" . "\\section*{%s}")
                  ("\\subsection{%s}" . "\\subsection*{%s}")
                  ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
                  ("\\paragraph{%s}" . "\\paragraph*{%s}")
                  ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
#+end_src

This uses the beautiful TeX-Gyre fonts. I haven't checked if they have a
Palatino clone--if so, I'd be inclined to use it.  If not, then you'll
want to replace tgtermes with mathpazo and give a bit more leading with 
\\linespread{1.05}.

You can put this code block in your local library of Babel and then load
it on a buffer-local basis, like this:

# Local Variables: 
# eval: (org-sbe "koma-article")
# End:

Beware of org-sbe, which used to be just sbe. You might need something
like this:

# eval: (and (fboundp 'org-sbe) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))

hth,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: Exporting text

[Peter Davis]

On Mon, Jan 27, 2014 at 03:41:29PM -1000, Thomas S. Dye wrote:
> Aloha Peter,

Aloha!

> 
> The Koma scripts for LaTeX use sans-serif headings.  Try this:

Excellent! Thank you, Thomas!

-pd


-- 
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com

Re: Exporting text

[Thomas S. Dye]

Aloha Peter,

Peter Davis <pfd@pfdstudio.com> writes:

> On Mon, Jan 27, 2014 at 03:41:29PM -1000, Thomas S. Dye wrote:
>> Aloha Peter,
>
> Aloha!
>
>> 
>> The Koma scripts for LaTeX use sans-serif headings.  Try this:
>
> Excellent! Thank you, Thomas!

The Tex-Gyre Palatino font is Pagella, \\usepackage{tgpagella}.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com