From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: using vref in latex export, and normal links in html export
Date: Sat, 12 Mar 2016 16:36:27 -0500 [thread overview]
Message-ID: <m2io0r4bvo.fsf@Johns-MacBook-Air.local> (raw)
In-Reply-To: <m2r3fh9h3o.fsf@charm-ecran.irisa.fr>
I guess these are defined in backends, e.g. org-latex-link.
Alan Schmitt writes:
> On 2016-03-11 16:05, Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> On 2016-03-11 15:02, John Kitchin <jkitchin@andrew.cmu.edu> writes:
>>
>>> Try:
>>>
>>> (setq org-latex-prefer-user-labels t)
>>>
>>> I think this does what you want for org 8.3.4 at least.
>>
>> Thank you! This is what I was missing.
>
> As a followup question, I read the documentation for `org-add-link-type`
> which says "Org mode has a built-in default for exporting links." What
> is the name of that function? I would like to change Eric's function to
> something like:
>
> #+begin_src elisp
> (org-add-link-type "vref" nil
> (lambda (path desc format)
> (cond
> ((eq format 'latex)
> (format "\\vref{%s}" path))
> (t (call org default)))))
> #+end_src
>
> I searched through ox.el but could not find that function.
>
> Thanks,
>
> Alan
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2016-03-12 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 10:20 using vref in latex export, and normal links in html export Alan Schmitt
2016-03-11 11:03 ` Eric S Fraga
2016-03-11 13:11 ` Alan Schmitt
2016-03-11 14:02 ` John Kitchin
2016-03-11 15:05 ` Alan Schmitt
2016-03-11 15:20 ` Alan Schmitt
2016-03-12 21:36 ` John Kitchin [this message]
2016-03-14 9:33 ` Alan Schmitt
2016-03-12 8:44 ` Stefan Nobis
2016-03-12 21:27 ` John Kitchin
2016-03-14 9:29 ` Alan Schmitt
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=m2io0r4bvo.fsf@Johns-MacBook-Air.local \
--to=jkitchin@andrew.cmu.edu \
--cc=alan.schmitt@polytechnique.org \
--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).