GNU Info

Info Node: (tramp)Top


Next: Overview Prev: (dir) Up: (dir)
Enter node , (file) or (file)node

TRAMP version 2.0.38 User Manual

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

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

   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

   The manual has been generated for Emacs.  If you want to read the
info pages for XEmacs, you should read in Note: Installation how to
create them.

   There is a mailing list for TRAMP, available at
<>, and archived at
`' as well
as the usual Savannah archives.

Copyright (C) 1999, 2000, 2001, 2002, 2003 Free Software Foundation,

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.1 or any later version published by the Free Software
     Foundation; with no Invariant Sections, with the Front-Cover texts
     being "A GNU Manual", and with the Back-Cover Texts as in (a)
     below.  A copy of the license is included in the section entitled
     "GNU Free Documentation License" in the Emacs manual.

     (a) The FSF's Back-Cover Text is: "You have freedom to copy and
     modify this GNU Manual, like GNU software.  Copies published by
     the Free Software Foundation raise funds for GNU development."

     This document is part of a collection distributed under the GNU
     Free Documentation License.  If you want to distribute this
     document separately from the collection, you can do so by adding a
     copy of the license to the document, as described in section 6 of
     the license.
What TRAMP can and cannot do.
For the end user:

Obtaining TRAMP
How to obtain TRAMP.
History of TRAMP.
Installing TRAMP with your Emacs.
Configuring TRAMP for use.
An overview of the operation of TRAMP.
Bug Reports
Reporting Bugs and Problems.
Frequently Asked Questions
Questions and answers from the mailing list.
Concept Index
An item for each concept.
For the developer:

Version Control
The inner workings of remote version control.
Files directories and localnames
How file names, directories and localnames are mangled and managed.
Debatable Issues and What Was Decided.
 --- The Detailed Node Listing ---

Installing TRAMP with your Emacs

Installation parameters
Parameters in order to control installation.
Load paths
How to plug-in TRAMP into your environment.
Japanese manual
Japanese manual.
Configuring TRAMP for use

Connection types
Types of connections made to remote machines.
Inline methods
Inline methods.
External transfer methods
External transfer methods.
Multi-hop Methods
Connecting to a remote host using multiple hops.
Default Method
Selecting a default method.
Customizing Methods
Using Non-Standard Methods.
Customizing Completion
Selecting config files for user/host name completion.
Remote Programs
How TRAMP finds and uses programs on the remote machine.
Remote shell setup
Remote shell setup hints.
Windows setup hints
Issues with Cygwin ssh.
Auto-save and Backup
Auto-save and Backup.

Filename Syntax
TRAMP filename conventions.
Multi-hop filename syntax
Multi-hop filename conventions.
Filename completion
Filename completion.
The inner workings of remote version control

Version Controlled Files
Determining if a file is under version control.
Remote Commands
Executing the version control commands on the remote machine.
Changed workfiles
Detecting if the working file has changed.
Checking out files
Bringing the workfile out of the repository.
Miscellaneous Version Control
Things related to Version Control that don't fit elsewhere.
Things related to Version Control that don't fit elsewhere

Remote File Ownership
How VC determines who owns a workfile.
Back-end Versions
How VC determines what release your RCS is.
How file names, directories and localnames are mangled and managed

Localname deconstruction
Breaking a localname into its components.

automatically generated by info2www version