X-Git-Url: http://git.hcoop.net/bpt/emacs.git/blobdiff_plain/7c33a0572280bdcf0583c5625cfda32f63fad56d..2ec1b5ee3464999a18b8197101e8bf08a3c564a8:/doc/misc/tramp.texi diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi index d307c1868a..4d853a5fb2 100644 --- a/doc/misc/tramp.texi +++ b/doc/misc/tramp.texi @@ -592,6 +592,10 @@ If both commands aren't available on the remote host, @value{tramp} transfers a small piece of Perl code to the remote host, and tries to apply it for encoding and decoding. +The variable @var{tramp-inline-compress-start-size} controls, whether +a file shall be compressed before encoding. This could increase +transfer speed for large text files. + @table @asis @item @option{rsh} @@ -625,11 +629,11 @@ Two other variants, @option{ssh1_old} and @option{ssh2_old}, use the @command{ssh1} and @command{ssh2} commands explicitly. If you don't know what these are, you do not need these options. -All the methods based on @command{ssh} have an additional kludgy -feature: you can specify a host name which looks like @file{host#42} -(the real host name, then a hash sign, then a port number). This -means to connect to the given host but to also pass @code{-p 42} as -arguments to the @command{ssh} command. +All the methods based on @command{ssh} have an additional feature: you +can specify a host name which looks like @file{host#42} (the real host +name, then a hash sign, then a port number). This means to connect to +the given host but to also pass @code{-p 42} as arguments to the +@command{ssh} command. @item @option{telnet} @@ -1230,7 +1234,9 @@ without bossing you around. You tell me whether it works @dots{} My suggestion is to use an inline method. For large files, external methods might be more efficient, but I guess that most people will -want to edit mostly small files. +want to edit mostly small files. And if you access large text files, +compression (driven by @var{tramp-inline-compress-start-size}) shall +still result in good performance. I guess that these days, most people can access a remote machine by using @command{ssh}. So I suggest that you use the @option{ssh} @@ -2125,10 +2131,9 @@ The backup file name of @file{@trampfn{su, root, localhost, The same problem can happen with auto-saving files. @ifset emacs -Since @value{emacsname} 21, the variable -@code{auto-save-file-name-transforms} keeps information, on which -directory an auto-saved file should go. By default, it is initialized -for @value{tramp} files to the local temporary directory. +The variable @code{auto-save-file-name-transforms} keeps information, +on which directory an auto-saved file should go. By default, it is +initialized for @value{tramp} files to the local temporary directory. On some versions of @value{emacsname}, namely the version built for Debian GNU/Linux, the variable @code{auto-save-file-name-transforms} @@ -2305,6 +2310,11 @@ using the @option{ssh} method to transfer files, and edit @file{.emacs} in my home directory I would specify the filename @file{@trampfn{ssh, daniel, melancholia, .emacs}}. +Finally, for some methods it is possible to specify a different port +number than the default one, given by the method. This is specified +by adding @file{#} to the host name, like in @file{@trampfn{ssh, +daniel, melancholia#42, .emacs}}. + @node Alternative Syntax @section URL-like filename syntax @@ -2749,17 +2759,13 @@ There is also a Savannah project page. @item Which systems does it work on? -The package has been used successfully on GNU Emacs 21, GNU Emacs 22, -GNU Emacs 23, XEmacs 21 (starting with 21.4), and SXEmacs 22. +The package has been used successfully on GNU Emacs 22, GNU Emacs 23, +XEmacs 21 (starting with 21.4), and SXEmacs 22. The package was intended to work on Unix, and it really expects a -Unix-like system on the remote end (except the @option{smb} method), -but some people seemed to have some success getting it to work on MS -Windows NT/2000/XP @value{emacsname}. - -There is some informations on @value{tramp} on NT at the following URL; -many thanks to Joe Stoy for providing the information: -@uref{ftp://ftp.comlab.ox.ac.uk/tmp/Joe.Stoy/} +Unix-like system on the remote end (except the @option{smb} and +@option{imap} methods), but some people seemed to have some success +getting it to work on MS Windows XP/Vista/7 @value{emacsname}. @item @@ -3339,7 +3345,7 @@ could write a script @file{emacsclient.sh}: @example #!/bin/sh -emacsclient @trampfn{ssh, `whoami`, `hostname --fqdn`, $1} +emacsclient @trampfn{ssh, $(whoami), $(hostname --fqdn), $1} @end example Then you must set the environment variable @code{EDITOR} pointing to