emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] IMPORTANT: (possibly) incompatible Change
Date: Thu, 01 Apr 2010 19:29:28 -0600	[thread overview]
Message-ID: <87wrwqlk07.fsf@gmail.com> (raw)
In-Reply-To: <F9BA0B81-AB97-46B4-8119-2CF962CCC3A5@gmail.com> (Carsten Dominik's message of "Wed, 31 Mar 2010 00:24:04 +0200")

[-- Attachment #1: Type: text/plain, Size: 114 bytes --]

After updating to the current git head, I have to make the following
changes for latex image generation to work.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: latex-packages-alist-fix.patch --]
[-- Type: text/x-diff, Size: 917 bytes --]

diff --git a/lisp/org.el b/lisp/org.el
index dc45871..443f881 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -2936,7 +2936,7 @@ appears on the page."
 ;; when formatting latex fragments.  Originally it was part of the
 ;; LaTeX exporter, which is why the name includes "export".
 (defcustom org-export-latex-default-packages-alist
-  '(("AUTO" . "inputenc")
+  '(("" . "inputenc")
     ("T1"   . "fontenc")
     (""     . "graphicx")
     (""     . "longtable")
@@ -15247,9 +15247,9 @@ Some of the options can be changed using the variable
 		  (concat "\n"
 			  (mapconcat (lambda(p)
 				       (if (equal "" (car p))
-					   (format "\\usepackage{%s}" (cadr p))
+					   (format "\\usepackage{%s}" (cdr p))
 					 (format "\\usepackage[%s]{%s}"
-						 (car p) (cadr p))))
+						 (car p) (cdr p))))
 				     (append
 				      org-export-latex-default-packages-alist
 				      org-export-latex-packages-alist)

[-- Attachment #3: Type: text/plain, Size: 2921 bytes --]


The "AUTO" change is because the AUTO.def file is not present on my
fairly complete Ubuntu texlive latex install

: ERROR: LaTeX Error: File `AUTO.def' not found.

The other change is because `org-export-latex-default-packages-alist' is
now a simple cons cell rather than a list so cadr was throwing errors.

It seems to me these may be general problems, not just specific to my
setup.

Best -- Eric

Carsten Dominik <carsten.dominik@gmail.com> writes:

> Dear all,
>
> I have just checked in an important change - if you use LaTeX
> export, you need to be aware of it.
>
> 1. Org contains now a much better system for handling special entities
>    that are written like LaTeX macros, for example \therefore,
> \emptyset,
>    etc.  I will write more about this in the release notes for 6.35.
> But
>    already now thanks go to Ulf Stegemann without whom this would not
>    have happened.
>
> 2. I could no longer keep the old setup for LaTeX export in
>    org-export-latex-classes.  The disadvantage was that whenever you
>    needed to make changes to the header, you would fix the value of
> this
>    variable so that any changes I'd make in the future would not be
> visible
>    to you.
>
>    The way this is solved now is (excerpt from the upcoming release
> notes)
>
> -----------------------------------------------------------------------------
> * =org-export-latex-classes= no longer should be customized for packages
>
> The HEADER part of this variable should now only contain the
> documentclass macro, nothing else - at least normally.  All the
> package calls via usepackage should go into
> org-export-latex-packages-alist.  I moved all the default packages
> that into a new variable org-export-latex-default-packages-alist.
> This will allow me to add more packages (as needed) in the
> future, withour requiring you to erase and then redo your
> configuration of org-export-latex-classes.
>
> So if you have customized this variable, please remove once more
> (hopefully for the last time) your customization, so that it can
> revert to its now much simpler default value.  Put all your
> package definitions into org-export-latex-packages-alist.
> I hope this works, and we will not get conflicts because of the
> sequence in which packages are called.  If there are problems,
> please let me know so that we can find a solution.
> -----------------------------------------------------------------------------
>
> I have not yet put this onto the master branch, but I will soon.
> If you want to help testing this new setup, please check out the branch
> new-entity-support from the git repo and let me know if you run into any
> problems.
>
> Thanks!
>
> - Carsten (and Ulf)
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[-- Attachment #4: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  parent reply	other threads:[~2010-04-02  1:29 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 22:24 IMPORTANT: (possibly) incompatible Change Carsten Dominik
2010-03-31  9:00 ` Chris Gray
2010-03-31 12:35   ` Carsten Dominik
2010-03-31 14:16     ` Eric Schulte
2010-03-31 14:18       ` Carsten Dominik
2010-03-31 18:41     ` Mark Elston
2010-04-01  6:59       ` Carsten Dominik
2010-04-01 11:13         ` Carsten Dominik
2010-04-01 16:17           ` Thomas S. Dye
2010-04-01 16:51             ` Carsten Dominik
2010-04-02 16:25               ` Thomas S. Dye
2010-04-02  1:17         ` Mark Elston
2010-04-02  7:55           ` Carsten Dominik
2010-04-03 18:49             ` Mark Elston
2010-04-03 22:50               ` Henri-Paul Indiogine
2010-04-03 22:55                 ` Carsten Dominik
     [not found]                   ` <87pr2gezp9.fsf@belvoir.org>
     [not found]                     ` <A3285E87-A435-4CD9-B5BF-13330A09CE63@gmail.com>
2010-04-04 17:36                       ` Henri-Paul Indiogine
2010-04-04 19:44                         ` Mark Elston
2010-04-06 11:57                   ` Karsten Heymann
2010-04-06 14:53                     ` Carsten Dominik
2010-04-03 22:57               ` Carsten Dominik
2010-04-03 23:25                 ` Mark Elston
2010-04-04  0:14                   ` Carsten Dominik
2010-04-04  5:47                     ` Nick Dokos
2010-04-04  6:39                       ` Carsten Dominik
2010-04-06 12:30         ` Karsten Heymann
2010-04-06 14:53           ` Carsten Dominik
2010-04-06 16:03             ` Karsten Heymann
2010-04-06 16:23               ` Carsten Dominik
2010-04-06 16:50                 ` Karsten Heymann
2010-04-06 18:30                   ` Robert Klein
2010-04-06 18:48                     ` Thomas S. Dye
2010-04-07  7:37                       ` Carsten Dominik
2010-04-07  8:22                         ` Karsten Heymann
2010-04-07  8:47                           ` Carsten Dominik
2010-04-07 10:31                             ` Karsten Heymann
2010-04-07 15:51                               ` Thomas S. Dye
2010-04-07 16:00                                 ` Carsten Dominik
2010-04-10 17:30                           ` Mark Elston
2010-04-10 20:01                             ` Thomas S. Dye
2010-04-11  3:40                               ` Mark Elston
2010-04-07  8:16                       ` Karsten Heymann
2010-04-07  7:38                     ` Carsten Dominik
2010-04-07  9:15                   ` Ulf Stegemann
2010-04-07 10:30                     ` Karsten Heymann
2010-04-07 11:58                       ` Ulf Stegemann
2010-04-07 12:24                         ` Karsten Heymann
2010-04-02  1:29 ` Eric Schulte [this message]
2010-04-02  2:47   ` [PATCH] " Mark Elston
2010-04-02  5:38   ` Carsten Dominik
2010-04-03 16:20 ` Henri-Paul Indiogine
2010-04-03 16:55   ` Carsten Dominik
2010-04-03 17:19     ` Xiao-Yong Jin
2010-04-06 10:25       ` Carsten Dominik

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=87wrwqlk07.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=carsten.dominik@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 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).