From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: bug#16751: 24.3.50; Export during Org export to HTML Date: Tue, 25 Feb 2014 19:04:10 +0100 Message-ID: <87vbw3t6g5.fsf@gmail.com> References: <86fvnmoxyp.fsf@somewhere.org> <86txbwlkeh.fsf@somewhere.org> <83ha7w75sc.fsf@gnu.org> <86wqgk7npj.fsf@somewhere.org> <86mwhf4jpo.fsf@somewhere.org> <834n3n17vg.fsf@gnu.org> <87ob1vnml6.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33461) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIMMT-0001SH-Kf for emacs-orgmode@gnu.org; Tue, 25 Feb 2014 13:04:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIMMN-0002cI-El for emacs-orgmode@gnu.org; Tue, 25 Feb 2014 13:04:09 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87ob1vnml6.fsf@bzg.ath.cx> (Bastien's message of "Tue, 25 Feb 2014 18:12:05 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Sebastien Vauban , 16751@debbugs.gnu.org, Eli Zaretskii Hello, Bastien 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