From: Aaron Ecay <aaronecay@gmail.com>
To: Oleh Krehel <ohwoeowho@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Conditional link export?
Date: Fri, 06 Nov 2015 13:24:09 +0000 [thread overview]
Message-ID: <878u6buupy.fsf@gmail.com> (raw)
In-Reply-To: <87ziyri8lk.fsf@gmail.com>
Hi Oleh,
One approach would be to use a parse-tree filter to change one kind of
link into another. Something like the following (not tested):
,----
| (defun awe/change-info-links (tree backend _info)
| (org-element-map tree 'link
| (lambda (link)
| (when (org-export-derived-backend-p backend 'html)
| (let* ((target (org-element-property :path link))
| (parts (split-string target "#")))
| (org-element-put-property link :type "https")
| (org-element-put-property
| link :path
| (format
| "//www.gnu.org/software/emacs/manual/html_node/%s/%s.html"
| (nth 0 parts)
| (nth 1 parts)))))))
| tree)
| (add-to-list 'org-export-filter-parse-tree-functions #'awe/change-info-links)
`----
This finds info links in the buffer, and converts them to http ones for
html export.
Exercises for the reader:
- Handle the case of info links with no “#”
- Link to manuals as http links in the document, and convert only the
relevant http links to info links for info export.
Hope this helps,
--
Aaron Ecay
next prev parent reply other threads:[~2015-11-06 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 13:02 Conditional link export? Oleh Krehel
2015-11-06 13:24 ` Aaron Ecay [this message]
2015-11-06 13:26 ` Aaron Ecay
2015-11-07 13:05 ` Oleh Krehel
2015-11-07 14:21 ` Aaron Ecay
2015-11-07 16:23 ` Achim Gratz
2015-11-08 14:09 ` Oleh Krehel
2015-11-08 14:27 ` Nicolas Goaziou
2015-11-08 14:56 ` Oleh Krehel
2015-11-08 15:04 ` Nicolas Goaziou
2015-11-08 15:35 ` Oleh Krehel
2015-11-08 16:06 ` Nicolas Goaziou
[not found] ` <m2k2ps9x9o.fsf@andrew.cmu.edu>
[not found] ` <8737wg6zi3.fsf@nicolasgoaziou.fr>
[not found] ` <m2ziy6vsw2.fsf@andrew.cmu.edu>
[not found] ` <87io4tpsu2.fsf@nicolasgoaziou.fr>
2015-11-22 23:08 ` John Kitchin
2015-11-08 18:03 ` Aaron Ecay
2015-11-06 13:28 ` John Kitchin
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=878u6buupy.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ohwoeowho@gmail.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).