[Top] [Contents] [Index] [ ? ]

TRAMP User Manual

This file documents TRAMP version 2.0.22, a remote file editing package for Emacs.

TRAMP stands for `Transparent Remote (file) Access, Multiple Protocol'. This package provides remote file editing, similar to Ange-FTP.

The difference is that Ange-FTP uses FTP to transfer files between the local and the remote host, whereas TRAMP uses a combination of rsh and rcp or other work-alike programs, such as ssh/scp.

You can find the latest version of this document on the web at http://www.freesoftware.fsf.org/tramp/.

This manual is also available as a Japanese translation.

The latest release of TRAMP is available for download, or you may see 3. Obtaining TRAMP. for more details, including the CVS server details.

TRAMP also has a Savannah Project Page.

There is a mailing list for TRAMP, available at tramp-devel@mail.freesoftware.fsf.org, and archived at http://www.mail-archive.com/emacs-rcp@ls6.cs.uni-dortmund.de/ as well as the usual Savannah archives.

1. An overview of TRAMP  What TRAMP can and cannot do.
2. Copying.  The license for this documentation.

For the end user:
3. Obtaining TRAMP.  How to obtain TRAMP.
4. History of TRAMP  
5. Installing TRAMP into Emacs.  Installing TRAMP with your Emacs.
6. Configuring TRAMP for use  
7. Using TRAMP  An overview of the operation of TRAMP.
8. Reporting Bugs and Problems  
9. Frequently Asked Questions  Questions and answers from the mailing list.

For the developer:
10. The inner workings of remote version control  
11. How file names, directories and paths are mangled and managed.  
12. Debatable Issues and What Was Decided  

 -- The Detailed Node Listing ---

Configuring TRAMP for use

6.1 Types of connections made to remote machines.  
6.2 Inline methods  
6.3 External transfer methods  
6.4 Connecting to a remote host using multiple hops  
6.5 Selecting a default method  
6.6 Using Non-Standard Methods  
6.7 Selecting config files for user/host name completion  
6.8 How TRAMP finds and uses programs on the remote machine.  
6.9 Remote shell setup hints  
6.10 Issues with Cygwin ssh  

Using TRAMP

7.1 TRAMP filename conventions  
7.2 Multi-hop filename conventions  
7.3 Filename completion  
7.4 Dired  

The inner workings of remote version control

10.1 Determining if a file is under version control  
10.2 Executing the version control commands on the remote machine  
10.3 Detecting if the working file has changed  
10.4 Bringing the workfile out of the repository  
10.5 Things related to Version Control that don't fit elsewhere  

Things related to Version Control that don't fit elsewhere

10.5.1 How VC determines who owns a workfile  
10.5.2 How VC determines what release your RCS is  

How file names, directories and paths are mangled and managed.

11.1 Breaking a path into its components.  



This document was generated by James LewisMoss on November, 11 2002 using texi2html