X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=man%2Fxemacs%2Ffiles.texi;h=1d813001938bd50bf0863c6c6454c3d242b1392a;hb=d8654f7c5ad0c04060008c6fbbd90add1f4537e3;hp=7ca98a7948540ec49d947dafab77fc5d27033257;hpb=6883ee56ec887c2c48abe5b06b5e66aa74031910;p=chise%2Fxemacs-chise.git.1

diff --git a/man/xemacs/files.texi b/man/xemacs/files.texi
index 7ca98a7..1d81300 100644
--- a/man/xemacs/files.texi
+++ b/man/xemacs/files.texi
@@ -10,6 +10,19 @@ commands apply directly to text in the buffer; that is, to the copy inside
 Emacs.  Your changes appear in the file itself only when you @dfn{save} the
 buffer back into the file.
 
+@cindex files, remote
+@cindex remote files
+  Emacs is also able to handle ``remote files'' which are stored on
+other hosts.  Not only is Emacs somewhat aware of the special issues
+involved with network file systems, but it can also use FTP and ssh (or
+rsh) to make local copies of the files, and refresh them on the remote
+host automatically when you save the buffer.  The FTP interface is
+provided by the standard @samp{efs} package @ref{Top, EFS, , efs}.  The
+ssh/rsh interface is provided by the optional @samp{tramp} package
+@ref{Top, TRAMP, , tramp}.  These packages attempt to implement all of
+the operations described below, making remote file use transparent
+(except for unavoidable network delays).
+
   In addition to visiting and saving files, Emacs can delete, copy, rename,
 and append to files, and operate on file directories.
 
@@ -43,6 +56,17 @@ file name is the name of the file visited in the current buffer; this
 makes it easy to operate on that file with any of the Emacs file
 commands.
 
+The syntax for accessing remote files unfortunately varies depending on
+the method used.  The syntax for using FTP is
+@samp{/@var{user}@@@var{remote-host}:@var{path-on-remote-host}}.  The
+syntax for using ssh is
+@samp{/[@var{user}@@@var{remote-host}]@var{path-on-remote-host}}.
+
+  In both cases the @samp{@var{user}@@} portion is optional (it defaults
+to your local user name).  @var{path-on-remote-host} may use the
+@samp{~} notation to indicate @var{user}'s home directory on the remote
+host.  The default file name will reflect the remote host information.
+
 @vindex default-directory
   Each buffer has a default directory, normally the same as the
 directory of the file visited in that buffer.  When Emacs reads a file
@@ -59,6 +83,10 @@ which does not specify a directory, it is short for @file{/u/rms/gnu/foo}.
 @samp{../.login} would stand for @file{/u/rms/.login}.  @samp{new/foo}
 would stand for the filename @file{/u/rms/gnu/new/foo}.
 
+  When visiting a remote file via EFS or TRAMP, the remote directory
+becomes the default directory (@pxref{Visiting}) for that buffer, just
+as a local directory would.
+
 @vindex default-directory-alist
 The variable @code{default-directory-alist} takes an alist of major
 modes and their opinions on @code{default-directory} as a Lisp
@@ -212,8 +240,10 @@ non-@code{nil}, the @code{find-file} command will check the
 @code{buffer-file-truename} of all visited files when deciding whether a
 given file is already in a buffer, instead of just
 @code{buffer-file-name}.  If you attempt to visit another file which is
-a hard-link or symbolic-link to a file that is already in a buffer, the
-existing buffer will be found instead of a newly created one.
+a symbolic link to a file that is already in a buffer, the existing
+buffer will be found instead of a newly created one.  This works if any
+component of the pathname (including a non-terminal component) is a
+symbolic link as well, but doesn't work with hard links (nothing does).
 
 @cindex creating files
    If you want to create a file, just visit it.  Emacs prints
@@ -477,8 +507,8 @@ The values are used just after a new backup version is made;
 that newly made backup is included in the count in @code{kept-new-versions}.
 By default, both variables are 2.
 
-@vindex trim-versions-without-asking
-  If @code{trim-versions-without-asking} is non-@code{nil},  excess
+@vindex delete-old-versions
+  If @code{delete-old-versions} is non-@code{nil},  excess
 middle versions are deleted without notification.  If it is @code{nil}, the
 default, you are asked whether the excess middle versions should
 really be deleted.