From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: why prepend "file://" to abs paths in html output?
Date: Fri, 7 Jul 2017 20:38:12 -0400 [thread overview]
Message-ID: <CAN_Dec9ht7PM0P6zZX0-9RXABFmjmeY0FLQRdN4uw_ffGHr3DA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
in org-html-link local links of the form
"/some/path/to/file"
are rewritten as
"file:///some/path/to/file".
This makes it difficult to write root-relative URL's in the way that one
might expect to be able to (so that export produces links like
<img src="/static/images/unicorn.jpg"/>
Is this really the most desirable behaviour? In html export, at least, I
would think most users would want to allow links of the kind I described.
But this seems like a conscious design decision; cf. these lines from
org-html-link:
;; If file path is absolute, prepend it with protocol
;; component - "file://".
(cond
((file-name-absolute-p raw-path)
(setq raw-path (org-export-file-uri raw-path)))
((and home use-abs-url)
(setq raw-path (concat (file-name-as-directory home) raw-path))))
I'm wondering whether a user oculd at least set a defcustom to control this
behaviour.
Thanks,
Matt
[-- Attachment #2: Type: text/html, Size: 1369 bytes --]
next reply other threads:[~2017-07-08 0:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:38 Matt Price [this message]
2017-07-08 10:33 ` why prepend "file://" to abs paths in html output? 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
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=CAN_Dec9ht7PM0P6zZX0-9RXABFmjmeY0FLQRdN4uw_ffGHr3DA@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).