emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Sebastien Vauban <sva-news@mygooglest.com>,
	16751@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#16751: 24.3.50; Export during Org export to HTML
Date: Tue, 25 Feb 2014 19:04:10 +0100	[thread overview]
Message-ID: <87vbw3t6g5.fsf@gmail.com> (raw)
In-Reply-To: <87ob1vnml6.fsf@bzg.ath.cx> (Bastien's message of "Tue, 25 Feb 2014 18:12:05 +0100")

Hello,

Bastien <bzg@altern.org> writes:

>> Ugh.  Bastien, could you (or someone else of Org developers) please
>> look into this?  Why does the URI above causes the recent version of
>> Org to pass an invalid file name such as
>>
>>    ///opt/tomcat/4/apache-tomcat-4.1.40/... to expand-file-name
>
> I will look into this, but I can't promise anything before next week.
>
> Thanks for the heads up,

A quick analysis.

    file:path

is a valid file link type in Org. Therefore,

    file:///opt/tomcat/4/apache-tomcat-4.1.40/webapps/../user_projects/GHIJSP2/deploy/WEB-INF/sharedfiles/resources/FR/domVal.xml

is parsed as a file link with path:

    ///opt/tomcat/4/apache-tomcat-4.1.40/webapps/../user_projects/GHIJSP2/deploy/WEB-INF/sharedfiles/resources/FR/domVal.xml

This path passes `file-name-absolute-p' predicate, so "ox-html.el"
concatenates "file://" to

  (expand-file-name path)

Since path is absolute, per `file-name-absolute-p', `expand-file-name'
is probably needed for its "and canonicalize it" part.

Note that other export back-ends, like, "ox-md.el", also use this
construct.

FWIW, I don't see any wrong behaviour here (except that "file://" should
probably not be prepended to path in this case).


Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2014-02-25 18:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86fvnmoxyp.fsf@somewhere.org>
     [not found] ` <mailman.15076.1392372434.10748.bug-gnu-emacs@gnu.org>
     [not found]   ` <86txbwlkeh.fsf@somewhere.org>
     [not found]     ` <83ha7w75sc.fsf@gnu.org>
     [not found]       ` <86wqgk7npj.fsf@somewhere.org>
     [not found]         ` <mailman.15924.1393259115.10748.bug-gnu-emacs@gnu.org>
     [not found]           ` <86mwhf4jpo.fsf@somewhere.org>
     [not found]             ` <834n3n17vg.fsf@gnu.org>
2014-02-25 17:12               ` bug#16751: 24.3.50; Export during Org export to HTML Bastien
2014-02-25 17:49                 ` Eli Zaretskii
2014-02-25 18:04                 ` Nicolas Goaziou [this message]
2014-02-25 18:32                   ` Eli Zaretskii
2014-02-25 19:11                     ` Achim Gratz
     [not found]                   ` <83lhwzyrdw.fsf@gnu.org>
2014-02-25 18:41                     ` Glenn Morris
     [not found]                     ` <9e1tyrjar9.fsf@fencepost.gnu.org>
2014-02-25 20:53                       ` Eli Zaretskii
     [not found]                 ` <83ob1vytf5.fsf@gnu.org>
2014-03-01 11:53                   ` Eli Zaretskii
2014-03-21  8:17                     ` Bastien
2014-03-28 18:36                       ` Nicolas Goaziou
2014-04-10 21:03                         ` Nicolas Goaziou
2014-04-11  8:48                           ` Bastien

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=87vbw3t6g5.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=16751@debbugs.gnu.org \
    --cc=bzg@altern.org \
    --cc=eliz@gnu.org \
    --cc=sva-news@mygooglest.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).