From: David Maus <dmaus@ictsoc.de>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode ml <emacs-orgmode@gnu.org>
Subject: Re: Link descriptions
Date: Wed, 15 Dec 2010 20:34:17 +0100 [thread overview]
Message-ID: <87ipyu6dae.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <25BB08A1-CC74-44F6-A939-A57F54B2685B@tsdye.com>
[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]
At Tue, 14 Dec 2010 08:09:21 -1000,
Thomas S. Dye wrote:
>
> Aloha all,
>
> After reading through the documentation fairly carefully, link
> descriptions are yielding unexpected results. Perhaps I missed
> something?
>
> I have a link defined for citep:
>
> #+source: define-citep-link
> #+begin_src emacs-lisp
> (org-add-link-type
> "citep" 'ebib
> (lambda (path desc format)
> (cond
> ((eq format 'latex)
> (format "\\citep[%s]{%s}" desc path)))))
> #+end_src
>
> With input like [[citep:jones][Jones]], it works fine, yielding
> \citep[Jones]{jones}.
>
> My hope, however, is to pass page numbers in the description so with
> [[citep:jones][123]] I get \citep[123]{jones}. When I have a
> description like this, I get [[citep:jones]$^{123}$] instead.
>
> This looks like a bug to me (at least I wish it would work to pass
> page numbers to the \citep command). Have I overlooked a restriction
> on link descriptions?
This is a bug, but not related to links: The LaTeX exporter turns a
sequence like:
][\d+]
into
]$^{\d+}$
Where \d+ is a placeholder for one or more numbers.
The question I cannot answer (yet?) is: Why?
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-12-15 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 18:09 Link descriptions Thomas S. Dye
2010-12-15 19:34 ` David Maus [this message]
2010-12-16 3:33 ` Thomas S. Dye
2010-12-16 5:18 ` Alan L Tyree
2010-12-19 14:00 ` David Maus
2010-12-19 16:18 ` Thomas S. Dye
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=87ipyu6dae.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).