tramp version 2.0.55 User Manual

This file documents tramp version 2.0.55, a remote file editing package for GNU 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.gnu.org/software/tramp/.

The latest release of tramp is available for download, or you may see 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@gnu.org, and archived at the tramp Mail Archive. Older archives are located at SourceForge Mail Archive and The Mail Archive.

Copyright © 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 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.

• Overview: What tramp can and cannot do.

For the end user:

• Obtaining Tramp: How to obtain tramp.
• History: History of tramp.
• Configuration: Configuring tramp for use.
• Usage: 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.
• Issues: Debatable Issues and What Was Decided.
• GNU Free Documentation License: The license for this documentation.

--- The Detailed Node Listing ---

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.
• Password caching: Reusing passwords for several connections.
• 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.

Using tramp

• Filename Syntax: tramp filename conventions.
• Multi-hop filename syntax: Multi-hop filename conventions.
• Filename completion: Filename completion.
• Dired: Dired.
• Compilation: Compile remote files.

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.