Re: EFS 1.6 bug: copy-file to SAME NAME
sandy@ibm550.sissa.it
Wed, 23 Mar 1994 08:13:06 +0100
Martin,
On Mon, 21 Mar 1994 you wrote:
> If I do 'M-x copy-file SOME_FILE_ON_MY_LOCAL_MACHINE /REMOTE:',
> the file gets the name '.' on the new machine .
> This works nicely, if the remote machine is a UNIX one,
> but it really creates a file named ".;1" if the remote host is a VMS VAX
> machine.
> Of course, the file should keep its name (at least if possible,
> otherwise it should get an
> 'abbreviated unique' form)!
I agree that this is a bug, but it's not an efs bug. M-x copy-file in
FSF emacs 18 and 19 from FILENAME to DIR, does not interpret the
destination as DIR/FILENAME. This has nothing to do with local vs
remote; I believe that it's always the case. efs doesn't overload
copy-file, so there isn't much I can do about it in general.
You might experiment a bit to see what copy-file's behaviour is if you
give the destination a directory. I always get a file-exists-p
warning. Then, bug the FSF emacs people to change copy-file's
behaviour.
I could go ahead, and change the behaviour for remote directories
only, but would prefer to keep things consistent between remote and
local copies.
--sandy