(tramp.info)Top
Next: Copying Prev: (dir) Up: (dir)
TRAMP User Manual
*****************
TRAMP stands for `Transparent Remote (file) Access, Multiple
Protocol'. This package provides remote file editing, similar to
`ange-ftp' and `EFS'.
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'.
This is version $Revision: 2.11 $ of the TRAMP manual, last updated
on Sunday, 20 January, 2002.
You can find the latest version of this document on the web at
`http://tramp.sourceforge.net/'.
There is a mailing list for TRAMP, available at
<tramp-devel@lists.sourceforge.net>, and archived at
`http://www.mail-archive.com/emacs-rcp@ls6.cs.uni-dortmund.de/' as well
as the usual SourceForge archives.
Copying- TRAMP Copying conditions.
- Overview
- What TRAMP can and cannot do.
For the end user:
- Obtaining TRAMP
- How to obtain TRAMP.
- History
- History of TRAMP
- Installation
- Installing TRAMP with your (X)Emacs.
- 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.
For the developer:
- Version Control
- The inner workings of remote version control.
- Files directories and paths
- How file names, directories and paths are mangled and managed.
- Issues
-
--- 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.
- Remote Programs
- How TRAMP finds and uses programs on the remote machine.
- Remote shell setup
-
Using TRAMP
- Filename Syntax
- TRAMP filename conventions.
- Multi-hop filename syntax
- Multi-hop filename conventions
- Dired
- Dired and 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 paths are mangled and managed.
- Path deconstruction
- Breaking a path into it's components.
automatically generated by info2www