From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>,
Subhan Tindall <subhan.tindall@rentrakmail.com>
Subject: Re: pxref in texinfo export
Date: Mon, 25 Feb 2013 23:23:37 +0100 [thread overview]
Message-ID: <87d2vodod2.fsf@gmail.com> (raw)
In-Reply-To: <CAEWDx5c2+ocdYUYscRQc14Q=CQ_setfT-mRDzV0udnMe_qi1Yg@mail.gmail.com> (Jonathan Leech-Pepin's message of "Mon, 25 Feb 2013 17:06:03 -0500")
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> For @xref{} I would need to know if it was at the start of a sentence and
> followed
> by a comma or period.
> For @pxref{} I would need to determine if it was at end of sentence,
> mid sentence followed by a comma or within parentheses, and not preceeded by
> "see" or "see". Although even this would not suffice, since there are
> contexts where
> @ref{} is the better choice.
FWIW, from `org-texinfo-link',
(org-export-data (org-export-get-previous-element link info t) info)
will give you the exported string so far in the container element and
(org-export-data (org-export-get-next-element link info t) info)
will return the string that will follow your link.
You need to upgrade Org for the first snippet, as order for `o-e-g-p-e'
return value has changed.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-02-25 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 17:52 pxref in texinfo export Thomas S. Dye
2013-02-25 18:32 ` Jonathan Leech-Pepin
2013-02-25 18:40 ` Subhan Tindall
2013-02-25 18:48 ` Jonathan Leech-Pepin
2013-02-25 19:01 ` Subhan Tindall
2013-02-25 20:24 ` Jonathan Leech-Pepin
2013-02-25 20:29 ` Jonathan Leech-Pepin
2013-02-25 21:34 ` Subhan Tindall
2013-02-25 22:01 ` Jonathan Leech-Pepin
2013-02-25 21:38 ` Nicolas Goaziou
2013-02-25 21:48 ` Subhan Tindall
2013-02-25 22:06 ` Jonathan Leech-Pepin
2013-02-25 22:23 ` Nicolas Goaziou [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=87d2vodod2.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
--cc=subhan.tindall@rentrakmail.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).