TRAMP - Revision history

Elvince: /* "Waiting for prompts from remote shell" message error */

2016-06-01T11:01:35Z

"Waiting for prompts from remote shell" message error

Elvince: Tramp debug: waiting for prompts

2016-06-01T10:43:40Z

Tramp debug: waiting for prompts

71.90.77.44: /* Edit current file as root */ simplify forms

2015-02-07T02:44:50Z

Edit current file as root: simplify forms

Elvince: edit current file as root

2014-03-07T10:50:32Z

edit current file as root

Elvince: /* Multiple hops */ in emacs24 works great

2013-07-24T10:10:55Z

Multiple hops: in emacs24 works great

Ccharles at 17:59, 2 April 2012

2012-04-02T17:59:30Z

Francesco: completed infobox information

2012-04-02T06:36:47Z

completed infobox information

Alex: Add infobox

2012-03-28T17:19:33Z

Add infobox

Ccharles: /* Multiple hops */

2012-03-28T16:55:24Z

Multiple hops

InCognito at 03:01, 27 March 2012

2012-03-27T03:01:50Z

@@ Line 97: / Line 97: @@
 and try again.
-You could also change the prompt regexp that Tramp understands or change the host prompt depending on the connection type. For more configuration possibilities, see [https://stackoverflow.com/questions/6954479/emacs-tramp-doesnt-work this Stack Overflow answer].
+You could also change the prompt regexp that Tramp understands ('''M-x customize-variable RET tramp-terminal-prompt-regexp''') but that is discouraged, or change the host prompt depending on the connection type (Tramp terminal shall be 'dumb', check the variable tramp-terminal-type):
 [[Category:Remote Edit]]

@@ Line 84: / Line 84: @@
        (message "Current buffer does not have an associated file."))))
 </source>
 [[Category:Remote Edit]]

@@ Line 80: / Line 80: @@
    "Edit the file that is associated with the current buffer as root"
    (interactive)
-   (if (buffer-file-name)
+   (let ((filep (buffer-file-name)))
-      (progn
+    (if filep (find-file (concat "/sudo::" filep))
-        (setq file (concat "/sudo::" (buffer-file-name)))
+      (message "Current buffer does not have an associated file."))))
 </source>
 [[Category:Remote Edit]]

← Older revision		Revision as of 10:50, 7 March 2014
Line 69:		Line 69:

	The <tt>plink</tt> method built into TRAMP can be used as a mostly drop-in replacement for SSH connections. It uses <tt>plink.exe</tt> from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY suite of tools], which must be installed separately.		The <tt>plink</tt> method built into TRAMP can be used as a mostly drop-in replacement for SSH connections. It uses <tt>plink.exe</tt> from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY suite of tools], which must be installed separately.
		+
		+	== Tips and tricks ==
		+
		+	=== Edit current file as root ===
		+
		+	Use the function below to open the current file as root:
		+
		+	<source lang="lisp">
		+	(defun edit-current-file-as-root ()
		+	"Edit the file that is associated with the current buffer as root"
		+	(interactive)
		+	(if (buffer-file-name)
		+	(progn
		+	(setq file (concat "/sudo::" (buffer-file-name)))
		+	(find-file file))
		+	(message "Current buffer does not have an associated file.")))
		+	</source>

	[[Category:Remote Edit]]		[[Category:Remote Edit]]

← Older revision		Revision as of 10:10, 24 July 2013
Line 17:		Line 17:

	== Multiple hops ==		== Multiple hops ==
		+
		+	=== No config in Emacs24 ===
		+
		+	As of Emacs 24, an analog of the old multi-hop syntax has been layered on top of the modern '''tramp-default-proxies-alist''' approach, meaning that you can once again perform multi-hops without any prior configuration. For details, see:
		+	{{Keys \| C-hig}} (tramp) Ad-hoc multi-hops RET
		+
		+	With the new syntax, each 'hop' is separated by '''\|''' (pipe). In this instance, it would look like:
		+
		+	{{Keys \| C-xC-f}} /ssh:user@server\|sudo:server:/home/user/file RET
		+
		+	As this still uses the proxy mechanism underneath,
		+	{{Keys \| C-hv}} tramp-default-proxies-alist RET
		+	should now include the value:
		+	<code>("server" "root" "/ssh:user@server:")</code>
		+
		+	Meaning that the proxy <code>/ssh:user@server:</code> is going to be used whenever you request a file as <code>root@server</code>.
		+
		+	Something important to note here is that you usually don't need to specify ''server'' in the ''sudo:server'' part -- and indeed ''sudo::'' will still work in a sense -- however if you do that then the dynamic proxy created will contain the hostname you originated from rather than the host you connected to, so I would recommend being explicit; otherwise it will not only look confusing (as the wrong host will be displayed in filenames), but it will also mean that subsequent attempts to use ''sudo::'' on the localhost will be proxied to this remote server!
		+
		+	=== Configuration for all emacs versions ===

	To set up multiple hop connections you will need to do a little bit of configuration.		To set up multiple hop connections you will need to do a little bit of configuration.

@@ Line 10: / Line 10: @@
 Some of the things that TRAMP can do include:
-* Editing files on a remote development server over SSH (e.g. <tt>/ssh:remote-user@remote.box:/path/to/my/file</tt>)
+* Editing files on a remote development server over SSH (e.g. {{Filename|/ssh:remote-user@remote.box:/path/to/my/file}})
-* Editing files on your local machine as root via sudo (e.g. <tt>/sudo::/etc/some/config/file</tt>)
+* Editing files on your local machine as root via sudo (e.g. {{Filename|/sudo::/etc/some/config/file}})
 * Editing files on a remote server as root via sudo over an SSH connection from another remote machine that exists within a DMZ (requires some configuration, see below)
@@ Line 20: / Line 20: @@
 To set up multiple hop connections you will need to do a little bit of configuration.
-As an example, let's assume that you want to edit a file located at <tt>/etc/httpd/conf/httpd.conf</tt> as root on a remote server at dev.example.com. You have a regular user account <tt>chris</tt> on the development sever, but you need to use sudo to gain root access before editing the file.
+As an example, let's assume that you want to edit a file located at {{Filename|/etc/httpd/conf/httpd.conf}} as root on a remote server at dev.example.com. You have a regular user account <tt>chris</tt> on the development sever, but you need to use sudo to gain root access before editing the file.
 Put the following into your configuration files:
@@ Line 38: / Line 38: @@
 After this is evaluated, Emacs knows that the hostname dev.example.com must be accessed over SSH by a user called chris.
-If you now try to find <tt>/sudo:dev.example.com:/etc/httpd/conf/httpd.conf</tt> Emacs will automatically create the SSH connection first, prompting you for your password if necessary. Then it will prompt you for your sudo password. Once this is all done you will be able to modify the buffer as necessary. Saving the buffer will do what you expect: it will update the file on the remote server.
+If you now try to find {{Filename|/sudo:dev.example.com:/etc/httpd/conf/httpd.conf}} Emacs will automatically create the SSH connection first, prompting you for your password if necessary. Then it will prompt you for your sudo password. Once this is all done you will be able to modify the buffer as necessary. Saving the buffer will do what you expect: it will update the file on the remote server.
 It is also possible to configure partial domains, for instance in case you need an SSH connection before modifying anything on <tt>*.example.com</tt>.

@@ Line 2: / Line 2: @@
 |name=TRAMP
 |description=Edit files on remote systems
-|in_emacs=since forever?
+|source=http://savannah.gnu.org/projects/tramp
 }}

← Older revision		Revision as of 17:19, 28 March 2012
Line 1:		Line 1:
		+	{{Package
		+	\|name=TRAMP
		+	\|description=Edit files on remote systems
		+	\|in_emacs=since forever?
		+	}}
		+
	Emacs' TRAMP feature (Transparent Remote file Access, Multiple Protocol) is an extremely powerful tool for editing files that exist on remote systems, or require access using a different user account from your main Emacs session, or both.		Emacs' TRAMP feature (Transparent Remote file Access, Multiple Protocol) is an extremely powerful tool for editing files that exist on remote systems, or require access using a different user account from your main Emacs session, or both.

@@ Line 17: / Line 17: @@
 Put the following into your configuration files:
- ;; Guard to ensure that TRAMP is available
+<source lang="lisp">
- (if (locate-library "tramp")
+;; Guard to ensure that TRAMP is available
-     (eval-after-load "tramp"
+(if (locate-library "tramp")
+    (eval-after-load "tramp"
-       ;; The actual TRAMP configuration
-       '(add-to-list 'tramp-default-proxies-alist
+      ;; The actual TRAMP configuration
-                     '("\\`dev\\.example\\.com\\'"
+      '(add-to-list 'tramp-default-proxies-alist
-                       "\\`chris\\'"
+                    '("\\`dev\\.example\\.com\\'"
-                       "/ssh:%h:"))))
+                      "\\`chris\\'"
 After this is evaluated, Emacs knows that the hostname dev.example.com must be accessed over SSH by a user called chris.

← Older revision		Revision as of 03:01, 27 March 2012
Line 41:		Line 41:
	The <tt>plink</tt> method built into TRAMP can be used as a mostly drop-in replacement for SSH connections. It uses <tt>plink.exe</tt> from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY suite of tools], which must be installed separately.		The <tt>plink</tt> method built into TRAMP can be used as a mostly drop-in replacement for SSH connections. It uses <tt>plink.exe</tt> from the [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY suite of tools], which must be installed separately.

−	[[Category~~:Workflow~~:Remote ~~Editing~~]]	+	[[Category:Remote Edit]]