tag 355627 wontfix
--
The name alias occurs because said file has shell meta characters in it,
specifically, the "&". Since according to the RFC, all commands from
the mailcap file are to be passed to /bin/sh, including shell
meta-characters in the filename can cause problems.
Imagine trying to open a file named such:
picture; rm -rf / .jpg
You would end up trying to erase every file on your system. Thus,
mime-support creates an alias for any files with such characters.
The first thought of an alternative would be to simply escape the
meta-characters so the shell doesn't try to interpret them.
Unfortunately, the RFC did not address this issue but did state that the
command must be run exactly as-is with the needed substitutions. Thus,
quoting meta-characters may not work in all cases
image/jpeg: xv "%f" would be okay
but image/jpeg: xv '%f' would be wrong
In the latter case, the "\" quoting would be considered part of the
filename and said file would not be found.
Sorry, but there is no easy (or hard, for that matter) fix for this.
Best if you don't include such characters in your filenames.
Brian
( [EMAIL PROTECTED] )
-------------------------------------------------------------------------------
It seems that anything people have learned prior to puberty takes
on the
status of an immutable truth (this is something well understood by
parents,
governments, and religions). Rational explanations of why some previous
belief might be incompatible with the behavior of nature, and a careful
explanation of the actual behavior of nature are of little avail.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
