dired mode subshell doesn't handle strange names properly

dired mode subshell doesn't handle strange names properly

[Toby H Ferguson]

This bug report will be sent to the Free Software Foundation,
 not to your local site managers!!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

In GNU Emacs 20.4.1 (sparc-sun-solaris2.8, X toolkit)
 of Fri Sep 24 1999 on solaris

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

I created a directory called '-Djava' - I listed it using dired, but
when I went to do a 'dired-do-shell-command' on it (the command being
rm -rf), the command failed with the following output:

rm: illegal option -- D
rm: illegal option -- j
rm: illegal option -- a
rm: illegal option -- v
rm: illegal option -- a
usage: rm [-fiRr] file ...

This can be fixed by ensuring that the arguments are followed by '--'
- but I don't know if this is general. In general the filename strings
out to be marked as not to be interpreted at the underlying shell level.


Recent input:
f return escape ! r m SPC - r f SPC ' - D SPC backspace 
j a v a ' return g g escape ! r m SPC - r f SPC - - 
SPC - D J a v a backspace backspace backspace backspace 
j a v a return g escape x b u g tab C-h a b u g return 
C-x 1 C-x b * H SPC C-h a b u g return C-x o C-x 1 
C-v C-v C-v C-v escape x r e p o r t SPC e m SPC b 
SPC return

Recent messages:
Reading directory /opt/ias/ias/ias70/instances/...
Reading directory /opt/ias/ias/ias70/instances/...done
Quit
Loading apropos...
Loading apropos...done
Type C-x 4 b RET to restore the other window.  M-C-v to scroll the help.
Quit
Type C-x 1 to remove help window.  M-C-v to scroll the help.
Loading emacsbug...
Loading emacsbug...done

Re: dired mode subshell doesn't handle strange names properly

[Paul Jarc]

toby.h.ferguson@sun.com (Toby H Ferguson) wrote:
> I created a directory called '-Djava' - I listed it using dired, but
> when I went to do a 'dired-do-shell-command' on it (the command being
> rm -rf), the command failed with the following output:
>
> rm: illegal option -- D
> rm: illegal option -- j
> rm: illegal option -- a
> rm: illegal option -- v
> rm: illegal option -- a
> usage: rm [-fiRr] file ...
>
> This can be fixed by ensuring that the arguments are followed by '--'
> - but I don't know if this is general.

It would be better to add "./" to the beginning of the filename, just
in case rm doesn't understand "--".

> In general the filename strings out to be marked as not to be
> interpreted at the underlying shell level.

The shell isn't involved in this problem.  It's all in rm's argument
parsing.


paul