bug#16751: 24.3.50; Export during Org export to HTML

[Eli Zaretskii]

> From: "Sebastien Vauban" <sva-news@mygooglest.com>
> Cc: 16751@debbugs.gnu.org
> Date: Mon, 24 Feb 2014 12:30:00 +0100
> 
> (gdb) frame 2
> #2  0x01131397 in Fexpand_file_name (name=107130897, 
> default_directory=99518353) at c:/msys/home/dani/emacs/trunk/src/fileio.c:1484
> 1484      c:/msys/home/dani/emacs/trunk/src/fileio.c: No such file or 
> directory.
> (gdb) p name
> $1 = 107130897
> (gdb) xstring
> (gdb) source ~/.gdbinit
> Warning: /cygdrive/c/Program Files (x86)/emacs-trunk/bin/../lwlib: No such 
> file or directory.
> SIGINT is used by the debugger.
> Are you sure you want to change it? (y or n) [answered Y; input not from 
> terminal]
> Environment variable "DISPLAY" not defined.
> TERM = xterm-256color
> Breakpoint 1 at 0x10f0372: file c:/msys/home/dani/emacs/trunk/src/emacs.c, 
> line 351.
> Temporary breakpoint 2 at 0x1113e88: file 
> c:/msys/home/dani/emacs/trunk/src/sysdep.c, line 854.
> (gdb) xstring
> $2 = (struct Lisp_String *) 0x662b010
> "///opt/tomcat/4/apache-tomcat-4.1.40/webapps/../user_projects/GHIJSP2/deploy/WEB-INF/sharedfiles/resources/FR/domVal.xml"

I see the problem now, and will make sure Emacs won't crash when
handed such bogus file names.

However, there's most probably a bug in Org as well, since it isn't
supposed to produce such file names.  I suspect this was an
incorrectly processed file:// URL.  Any chance you could throw
together the shortest Org file with such a file name and a minimal
recipe to reproduce the problem starting from "emacs -Q"?  I'd like to
see how exactly this "file name" cam into existence.

> > Also, what does org-element-property return for this file name (that's
> > the argument passed to expand-file-name, I think)?
> 
> I tried to eval (org-element-property) on the file name, in the above
> Org file:
> 
> --8<---------------cut here---------------start------------->8---
> Debugger entered--Lisp error: (wrong-number-of-arguments (lambda (property 
> element) "Extract the value from the PROPERTY of an ELEMENT." (if (stringp 
> element) (get-text-property 0 property element) (plist-get (nth 1 element) 
> property))) 0)
>   org-element-property()
>   eval((org-element-property) nil)
>   eval-expression((org-element-property) nil)
>   call-interactively(eval-expression nil nil)
>   command-execute(eval-expression)
> --8<---------------cut here---------------end--------------->8---
> 
> Not what you wanted, for sure.

No, I meant to step in Edebug through org-html-link and see what is
the value of raw-path that org-element-property returns there.  But if
you can give me a small recipe and an Org file to go with it, I can do
that myself, thanks.