From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Accessing the communication channel from a link exporter
Date: Fri, 02 Sep 2016 08:30:02 -0400 [thread overview]
Message-ID: <m2lgzascvp.fsf@Johns-MacBook-Air.local> (raw)
In-Reply-To: <cu7d1knqxu8.fsf@systemreboot.net>
I think this is the kind of thing you can use a filter for, or a
function in the org-export-before-processing-hook to change the paths
prior to export.
Arun Isaac writes:
>> Out of curiosity, what kind of link are you using, that is dependant
>> about context ?
>
> Actually, I don't need the context of the link in the org document. I
> need some properties defined in the plist of the component in
> org-publish-project-alist. So, I use the info communication channel to
> access these properties.
>
> I maintain a few websites with org mode. When I publish an image link
> with org, the exported HTML contains the full filesystem path of the
> image. The page wouldn't work if I published it on the web. My link type
> needs to know the path of the web server's docroot to remove that
> component from the full filesystem path. This path is defined in one of
> the properties in org-publish-project-alist, and I need the info
> communication channel to access it.
--
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-09-02 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 11:57 Accessing the communication channel from a link exporter Arun Isaac
2016-09-01 16:39 ` Nicolas Goaziou
2016-09-01 18:27 ` Arun Isaac
2016-09-02 12:30 ` John Kitchin [this message]
2016-09-02 15:33 ` Arun Isaac
2016-09-02 16:33 ` John Kitchin
2016-09-03 18:35 ` Arun Isaac
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=m2lgzascvp.fsf@Johns-MacBook-Air.local \
--to=jkitchin@andrew.cmu.edu \
--cc=arunisaac@systemreboot.net \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).