From: Nick Dokos <nicholas.dokos@hp.com>
To: Andreas Willig <andreas.willig@canterbury.ac.nz>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Integration of RefTeX and LaTeX export
Date: Fri, 17 Feb 2012 12:59:58 -0500 [thread overview]
Message-ID: <2827.1329501598@alphaville> (raw)
In-Reply-To: Message from Andreas Willig <andreas.willig@canterbury.ac.nz> of "Fri, 17 Feb 2012 21:36:05 +1300." <A47458F1AE3BC545911B10628202E9D204D28DF6@ucexchange2.canterbury.ac.nz>
Andreas Willig <andreas.willig@canterbury.ac.nz> wrote:
> it is a version problem. I have just downloaded the latest version of
> org-mode (7.8.03) and now the handler gets called.
>
So what version were you using? The only likely fix I found was this
commit from almost two years ago:
,----
| commit 8a671f8d4da0066417d9dd78fffb42ea1fe9ec9d
| Author: Carsten Dominik <carsten.dominik@gmail.com>
| Date: Wed May 12 15:14:17 2010 +0200
|
| LaTeX export: Use special formatting by link type interface
|
| Patch by Christian Moe, who writes:
|
| > It looks like support for formatting custom link types in LaTeX export
| > is broken?
| >
| > I was trying to implement a custom link type with its own formatting
| > function for HTML and LaTeX export, following the steps in
| > org-bbdb.el.
| >
| > I've found that org-bbdb-export does not italicize bbdb links in
| > LaTeX, nor does my own org-cite-export turn my custom =cite:= links
| > into LaTeX =\cite{}= citations. Everything works fine in HTML export,
| > but in LaTeX all custom link types get formatted as =\texttt{descr}=.
| >
| > I see that org-export-as-html and org-export-as-docbook look up
| > org-link-protocols to get the function for formatting the link, but it
| > seems that org-export-as-latex doesn't.
| >
| >
`----
and git describe says:
,----
| $ git describe 8a671f8d
| release_6.36-19-g8a671f8
`----
so yours must have been pre-6.36 or thereabouts, i.e. probably whatever was
built-in with your (23.2-based?) emacs.
If you were indeed using such an ancient version, I think you will be
*much* happier with latest.
> Sorry for the fuss ...
>
No fuss, no muss.
Nick
next prev parent reply other threads:[~2012-02-17 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 20:59 Integration of RefTeX and LaTeX export Andreas Willig
2012-02-16 22:08 ` Thomas S. Dye
2012-02-17 4:46 ` Andreas Willig
2012-02-17 5:31 ` Nick Dokos
2012-02-17 7:39 ` Andreas Willig
2012-02-17 8:10 ` Andreas Willig
2012-02-17 8:36 ` Andreas Willig
2012-02-17 17:59 ` Nick Dokos [this message]
2012-02-17 19:12 ` Achim Gratz
2012-02-17 19:17 ` Nick Dokos
2012-03-23 16:14 ` Navigatable and exportable bib/notes links - Was: " Olivier Berger
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=2827.1329501598@alphaville \
--to=nicholas.dokos@hp.com \
--cc=andreas.willig@canterbury.ac.nz \
--cc=emacs-orgmode@gnu.org \
/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).