emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: nicholas.dokos@hp.com, SW <sabrewolfy@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Disable links in Latex export
Date: Thu, 26 Apr 2012 06:47:25 -0500	[thread overview]
Message-ID: <CA+M2ft-bfdn9Dod_HMisD6ndJT4hEbkjkaahnRk9Yf_wvnjV-g@mail.gmail.com> (raw)
In-Reply-To: <87vckmlvu0.fsf@ucl.ac.uk>

On Thu, Apr 26, 2012 at 3:51 AM, Eric Fraga <e.fraga@ucl.ac.uk> wrote:
> Nick Dokos <nicholas.dokos@hp.com> writes:
> [...]
>> If all you care about is the *appearance*, rather than the existence of
>> links, however, you can use hyperref package options to influence
>> that. For example
>>     \usepackage[pdfborder={0,0,0}]{hyperref}
>> will get rid of the red boxes around the links in the TOC: they are
>> still links, they are just not that obvious any more.  You can do that
>> by customizing the org-export-latex-default-packages-alist variable:
>> just add the above option (without the square brackets) to the hyperref
>> package entry.
> adding the line
> #+latex_header: \hypersetup{pdfborder={0,0,0}}
> in the org document should be sufficient?
> In practice, I actually do:
> #+latex_header: \hypersetup{colorlinks=true}

And red isn't my cup of tea, so I use:

#+LATEX_HEADER: \hypersetup{colorlinks=true,urlcolor=blue}

> which still colours the links but gets rid of the ugly boxes.
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs
> : using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

  reply	other threads:[~2012-04-26 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 17:08 Disable links in Latex export SW
2012-04-11 18:01 ` Nick Dokos
2012-04-26  8:51   ` Eric Fraga
2012-04-26 11:47     ` John Hendy [this message]
2012-05-29 12:17       ` SW
2012-05-29 12:12     ` SW
2012-05-29 12:08   ` SW

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:

  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=CA+M2ft-bfdn9Dod_HMisD6ndJT4hEbkjkaahnRk9Yf_wvnjV-g@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=sabrewolfy@gmail.com \


* 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


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).