From: Tim Cross <theophilusx@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Carsten Dominik <dominik@uva.nl>,
Org Mode <emacs-orgmode@gnu.org>,
Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: why prepend "file://" to abs paths in html output?
Date: Tue, 11 Jul 2017 08:12:20 +1000 [thread overview]
Message-ID: <877ezgym9n.fsf@gmail.com> (raw)
In-Reply-To: <877ezh51ns.fsf@nicolasgoaziou.fr>
Having seen the other posts on this, I think I'll need to spend more
time thinking about this and the various use cases. There is something
I'm having trouble putting my finger on which doesn't feel quite right,
but I feel I need to look more deeply into the whole idea of how to
export links generally. Originally, I was thinking just about HTML
export and just file:// vs site context specific links.
Based on what you have provided, this certainly does seem to address the
specific use case I was thinking of, but others have pointed out
additional considerations, so I'm now not sure if the suggested approach
won't improve one case while making others more difficult/restricted.
Tim
Nicolas Goaziou writes:
> Hello,
>
> Tim Cross <theophilusx@gmail.com> writes:
>
>> Perhaps we need a way to easily set a context for web exports. If the
>> context is set, then use it, otherwise, use file:/// (actually, I
>> thought this was already there, but it has been a while since I did html
>> exports where links were necessary).
>
> The following patch implements `org-html-root', which allows to export
> file links as root-relative URL. I'm not sure the docstring is clear
> enough, tho.
>
> Also, HTML publishing process always bind the above to publishing
> directory, without user intervention.
>
> So, basically, upon exporting the following document to HTML:
>
> #+html_link_root: /tmp/
> [[/tmp/unicorn.jpg]]
>
> the link becomes
>
> <img src="/unicorn.jpg" alt="unicorn.jpg" />
>
>
> WDYT?
>
> Regards,
--
Tim Cross
prev parent reply other threads:[~2017-07-10 22:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:38 why prepend "file://" to abs paths in html output? Matt Price
2017-07-08 10:33 ` Nicolas Goaziou
2017-07-08 12:37 ` Kaushal Modi
2017-07-08 14:08 ` Nicolas Goaziou
2017-07-08 14:19 ` Carsten Dominik
2017-07-08 19:13 ` Nicolas Goaziou
2017-07-08 23:37 ` Tim Cross
2017-07-09 10:45 ` Nicolas Goaziou
2017-07-10 12:53 ` Kaushal Modi
2017-07-10 13:31 ` Nicolas Goaziou
2017-07-10 13:58 ` Brett Viren
2017-07-10 19:54 ` Kaushal Modi
2017-07-10 21:44 ` Kaushal Modi
2017-07-13 12:39 ` Nicolas Goaziou
2017-07-13 12:50 ` Kaushal Modi
2017-07-13 12:55 ` Nicolas Goaziou
2017-07-13 13:01 ` Kaushal Modi
2017-07-13 13:14 ` Nicolas Goaziou
2017-07-13 12:46 ` Nicolas Goaziou
2017-07-10 22:12 ` Tim Cross [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=877ezgym9n.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--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).