Re: Dangerous behavior when copying to current directory

[Richard Stallman]

    Your fix works only for the case where a specified directory has no
    final slash.  But after invoking M-x copy-file or M-x rename-file
    the default initial value for the second argument has a final slash,
    e.g. `/tmp/'.  Since `copy-file' and `rename-file' have interactive
    specification `F' for the second argument, when they get called with
    the default value after typing RET, the second argument is already
    expanded to the wrong file name.

It seems to happen only in some conditions.  The first time I tried
this, it did not happen; the second time, it did.

I fixed this by setting up a new interactive spec.
However, I can't install it easily from here.