From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: ox-latex: Is \uline really right for underlining?
Date: Thu, 12 Dec 2013 14:47:57 +0800 [thread overview]
Message-ID: <CAFniQ7WqZNqfZx0vS-3NZDqcBSGSEVvSr=GnGy9085kf3_58xQ@mail.gmail.com> (raw)
In-Reply-To: <4b911e1e-49e6-4a80-b152-3b1910bb4a6d@dewdrop-world.net>
On Thu, Dec 12, 2013 at 10:40 AM, James Harkins
<jamshark70@dewdrop-world.net> wrote:
> On Wednesday, December 11, 2013 10:47:42 PM HKT, Nicolas Goaziou wrote:
>>>
>>> Is "ulem" one of the LaTeX export default packages?
>>
>> Yes, it is. See `org-latex-default-packages-alist'.
>
> Ah... I must have customized that at some point.
And... I just found why I had customized it. It was because of
hyperref's (idiotic) default behavior of drawing red boxes around
links.
I'm not sure how "ulem" didn't make it into my customized setting.
Maybe "ulem" was added to the default packages list after I made the
customization.
What's the best way to handle that? I really want the "hidelinks"
option for hyperref to be used globally. But, customizing
org-latex-default-packages-alist means that I will miss updates to
that variable in future org versions.
Should I leave org-latex-default-packages-alist alone, and add my own
entry for hyperref into org-latex-packages-alist? (Would there be any
ill effect from having two \usepackage{hyperref} lines in the
preamble, with different options?)
hjh
next prev parent reply other threads:[~2013-12-12 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:21 ox-latex: Is \uline really right for underlining? James Harkins
2013-12-11 14:47 ` Nicolas Goaziou
2013-12-12 2:40 ` James Harkins
2013-12-12 6:47 ` James Harkins [this message]
2013-12-12 7:02 ` Aaron Ecay
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='CAFniQ7WqZNqfZx0vS-3NZDqcBSGSEVvSr=GnGy9085kf3_58xQ@mail.gmail.com' \
--to=jamshark70@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@gmail.com \
/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).