I was hit by the fact that expand-file-name does not
work the same way as in Emacs. It returns the result in
backslash format in win32 and forward slashes in Unix. This is
a bit hard and ugly when I combine paths always with forward
slashes.
(expand that) + "path/here"
\that\dir/path/here
It also defeated In my code member and pushnew
tests now when everything was not in forward slash format.
Oh well...
In Emacs it always returns forward slashes which I think is
easy for a develooper.
Would it be possible to modify it so that expand-file-name had
an additional argument FORMAT that would control the path
expansion.
By default it would return always forward slashes to regain
Emacs compatibility. With extra argument:
FORMAT 'native as OS default. In Win32 \ in Unix /
'dos Explicit \ request
'unix Explicit / request
Jari
--
http://tiny-tools.sourceforge.net/