emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Denis Maier <denismaier@mailbox.org>
To: Bruce D'Arcus <bdarcus@gmail.com>,
	org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [org-cite, oc-csl] setting no-link parameter within document?
Date: Fri, 4 Jun 2021 14:01:12 +0200	[thread overview]
Message-ID: <cc6fc9ed-5f67-7891-2640-be50aa6e813f@mailbox.org> (raw)
In-Reply-To: <CAF-FPGMJ6uBQ9wi0rddSuNr0r4fdTnQ2jpDEqcp1wDFPpny7JA@mail.gmail.com>

Am 04.06.2021 um 13:50 schrieb Bruce D'Arcus:
> I see the processor has a org-cite-csl-link-cites defcustom to set
> this globally, but can one set it at the document level?
> Further explanation:
> The default hyperref settings in latex export in general are too much,
> with boxes everywhere and garish colors.
> When coupled with a note style with bibliography, like
> chicago-note-bibliography-16th-edition.csl, it's overwhelming, Notably
> each footnoted text becomes linked. And in that case, the linked data
> is redundant. Example and screenshots here:
> https://github.com/andras-simonyi/citeproc-el/issues/24
> So I can imagine a user generally leaving the defcustom set to true,
> but on individual documents (like with the chicago example) wanting to
> turn it off.
> Note that one can, per the thread I link to above, turn off links, or
> modify their colors, using hyperref. But that's specific to the latex
> export, and I don't think (?) there's an easy way to set that at the
> document level.

Ok, I first thought you can just add the configuration to the 
LATEX_HEADER keywords, but that won't work since everything in there is 
loaded before hyperref.

So, I guess a LATEX_HYPERSETUP could make sense?

In the meantime users can just use a hyperref.cfg file to store their 


> Bruce

  reply	other threads:[~2021-06-04 12:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 11:50 [org-cite, oc-csl] setting no-link parameter within document? Bruce D'Arcus
2021-06-04 12:01 ` Denis Maier [this message]
2021-06-04 12:18   ` Eric S Fraga
2021-06-04 12:20     ` Denis Maier
2021-06-04 13:16       ` Eric S Fraga
2021-06-04 12:24     ` Bruce D'Arcus
2021-06-04 12:51       ` Denis Maier
2021-06-04 12:59         ` Bruce D'Arcus
2021-06-04 13:28       ` Nicolas Goaziou

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=cc6fc9ed-5f67-7891-2640-be50aa6e813f@mailbox.org \
    --to=denismaier@mailbox.org \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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