From e598a60dc3f957b685eb26dbb83b4e544261e412 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 14 Jul 2003 15:53:56 +0000 Subject: [PATCH] (Changing Files): copy-file allows dir as NEWNAME. (Magic File Names): Specify precedence order of handlers. --- lispref/files.texi | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/lispref/files.texi b/lispref/files.texi index 4082268cd83..c61c9ad11d2 100644 --- a/lispref/files.texi +++ b/lispref/files.texi @@ -1276,7 +1276,9 @@ In an interactive call, this function prompts for @var{filename} and @deffn Command copy-file oldname newname &optional ok-if-exists time This command copies the file @var{oldname} to @var{newname}. An -error is signaled if @var{oldname} does not exist. +error is signaled if @var{oldname} does not exist. If @var{newname} +names a directory, it copies @var{oldname} into that directory, +preserving its final name component. If @var{time} is non-@code{nil}, then this function gives the new file the same last-modified time that the old one has. (This works on only @@ -2295,6 +2297,11 @@ this: The @var{handler} then needs to figure out whether to handle @var{filename} or @var{dirname}. +If the specified file name matches more than one handler, the one +whose match starts last in the file name gets precedence. This rule +is chosen so that handlers for jobs such as uncompression are handled +first, before handlers for jobs such as remote file access. + Here are the operations that a magic file name handler gets to handle: @ifnottex -- 2.39.2