Joe Hirn <joseph.h...@gmail.com> writes: > Hm. That's disappointing. I really prefer the original behavior. I don't > want to copy #+latex_header to get this default behavior into each of my > org-mode files. > > I guess I'll just have to maintain this by redefining the entire > org-latex-template function to look at my variable instead of the hard > coded string. A pain but apparently my own option.
Before doing so reread Nicholas' suggestion. I.e.: Set org-latex-with-hyperref to nil. Look at org-latex-classes and add your preferred hypersetup to a new class (note an Org LaTeX class is a predefined preamble in LaTeX terms). Set org-latex-default-class to your new class. If this is not flexible enough use a filter. Several filter examples modifying the preamble have been posted on this list. —Rasmus > On Mon, Feb 17, 2014 at 4:13 PM, Nicolas Goaziou <n.goaz...@gmail.com>wrote: > >> Hello, >> >> Joe Hirn <joseph.h...@gmail.com> writes: >> >> > Hello. I recently upgraded to org 8 from the builtin org (7.x) of Emacs >> > 24.3 and lost the ability to customize the \hypersetup block via the >> custom >> > var org-export-latex-hyperref-options-format. Platform is OSX, Emacs >> > installed via homebrew and org-mode updated via package.el. >> > >> > Org 7.x defines the var in org-latex.el. Because it's a builtin, the >> custom >> > var still displays in the 'org-latex-export group when configuring >> options. >> > However, the new export logic from ox-latex.el does not define this >> custom >> > var, nor does it respect the value if it is set. This is doubly confusing >> > because it appears the var is available, but it actually unused. >> >> The problem will go with the next Emacs release. >> >> > I found this thread from September which describes the same issue, but >> the >> > patch did not address adding the custom var back and seems to have died. >> > http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01364.html >> >> Actually, there is a way to ignore hypersetup block. See >> `org-latex-with-hyperref'. >> >> If you really want a custom command, I think it is better to first >> disable it with the variable aforementioned, then include your own >> with #+latex_header or in a custom latex class (see >> `org-latex-classes'). >> >> You can also use a filter to change it on the fly, but that would be >> less straightforward. >> >> >> Regards, >> >> -- >> Nicolas Goaziou >> -- El Rey ha muerto. ¡Larga vida al Rey!