emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Best way to include references/license
Date: Wed, 5 Nov 2014 09:38:26 -0500	[thread overview]
Message-ID: <CAA6UvuHAiJ3ckE8Uw7PW=Hvf7yWYxMNYyBWGA-KD7W6MavigrA@mail.gmail.com> (raw)
In-Reply-To: <86mw85agaj.fsf@example.com>

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

On Wed, Nov 5, 2014 at 9:11 AM, Sebastien Vauban <sva-news@mygooglest.com>
wrote:

> Jacob Gerlach wrote:
> > On Wed Nov 05 2014 at 4:22:06 AM Julien Cubizolles wrote:
> >
> >> Bracket links (like <<link>>) create a \texttt{} \hypertarget{} pair
> >> instead of a \label{} \ref{} pair in the latex file. Should I go with
> >> explicit \label{} \ref{} in the org file ?
> >
> > The \texttt{} is probably because org could not resolve a target from
> > your link. I can't help much with your problem, but see C-h
> > v org-latex-link-with-unknown-path-format RET for an idea of where the
> > \texttt{} comes from.
>
> FWIW, the value I set in my .emacs file is "\\colorbox{red}{%s}", so
> that it stands out in the exported document.
>
I take it one step further and use \BADLINK. This causes pdflatex to
complain, so the export fails. No need to then try to catch it in the
exported document.

There was some recent discussion of patching the exporter to report errors
on unresolved links:
http://lists.gnu.org/archive/html/emacs-orgmode/2014-09/msg00880.html

Jake

[-- Attachment #2: Type: text/html, Size: 1700 bytes --]

      reply	other threads:[~2014-11-05 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  9:21 Best way to include references/license Julien Cubizolles
2014-11-05 13:26 ` Nicolas Goaziou
2014-11-06 17:06   ` Julien Cubizolles
2014-11-06 18:27     ` Nicolas Goaziou
2014-11-09 20:51       ` Julien Cubizolles
2014-11-05 13:57 ` Jacob Gerlach
2014-11-05 14:11   ` Sebastien Vauban
2014-11-05 14:38     ` Jacob Gerlach [this message]

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='CAA6UvuHAiJ3ckE8Uw7PW=Hvf7yWYxMNYyBWGA-KD7W6MavigrA@mail.gmail.com' \
    --to=jacobgerlach@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.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).