From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-15?q?Gro=DFjohann?=) Newsgroups: gmane.emacs.devel Subject: Re: Integrate Tramp Date: Fri, 21 Jun 2002 17:50:07 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: References: <200206171631.g5HGVBM13861@aztec.santafe.edu> <200206190223.g5J2NlQ15963@aztec.santafe.edu> <200206201434.g5KEYru18709@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1024674699 30708 127.0.0.1 (21 Jun 2002 15:51:39 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 21 Jun 2002 15:51:39 +0000 (UTC) Cc: rms@gnu.org, miles@gnu.org, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17LQhG-0007zB-00 for ; Fri, 21 Jun 2002 17:51:38 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17LR9U-0000B3-00 for ; Fri, 21 Jun 2002 18:20:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17LQhH-0005ew-00; Fri, 21 Jun 2002 11:51:39 -0400 Original-Received: from waldorf.cs.uni-dortmund.de ([129.217.4.42]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17LQgQ-0005bF-00; Fri, 21 Jun 2002 11:50:46 -0400 Original-Received: from lothlorien.cs.uni-dortmund.de (lothlorien [129.217.19.67]) by waldorf.cs.uni-dortmund.de with ESMTP id g5LFoDb08835; Fri, 21 Jun 2002 17:50:13 +0200 (MES) Original-Received: from lucy.cs.uni-dortmund.de (lucy [129.217.19.80]) by lothlorien.cs.uni-dortmund.de id RAA13079; Fri, 21 Jun 2002 17:50:07 +0200 (MET DST) Original-Received: by lucy.cs.uni-dortmund.de (Postfix, from userid 6104) id 54D2A3B5E4; Fri, 21 Jun 2002 17:50:07 +0200 (CEST) Original-To: bob@rattlesnake.com In-Reply-To: ("Robert J. Chassell"'s message of "Fri, 21 Jun 2002 14:55:09 +0000 (UTC)") Original-Lines: 79 User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.3.50 (i686-pc-linux-gnu) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:5060 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5060 "Robert J. Chassell" writes: > Thank you! Now I understand. > > From this I infer that this means that you can *not* use a method like > `smx' or `su' in a multi-hop connection. Instead, you must use only a > `plain' method, such as `ssh' or `telnet'. The `multi'/`multiu' > distinction tells the most remote machine what to use. Am I right? Actually, the list of "hop methods" is in the variable tramp-multi-connection-function-alist. The list is also given in the node "(tramp)Multi-hop Methods" in the info file. > In other words, my example should look like this: > > /[multiu]ssh#bob@fencepost.gnu.org|ssh#bob@titan.berkshire.net:/home/bob/ This looks correct. > If so, I am a little bit bothered, since it would seem easier to me > > * to provide only one kind of `multi' tag, Indeed, this would be good. This goes well together with the auto-detection of base64 encoding versus uuencode encoding that I've put on my todo list. > * which would be optional, since a `multi' tag is no longer needed, Yes, it wouldn't be so difficult to change Tramp so that it looks for "|" to figure out if it's a single-hop or multi-hop filename. > * to tell users that they need only provide `plain' methods on the > intermediary hops, I've tried to do that in the above mentioned info node. > * but let users provide methods like `smx' or `tu' if they wish, > since they may simply be copying the types used for single hop > connections. (The `mimencode' or `uuencode' commands can be > ignored for intermediary hops.) The "hop methods" are treated quite differently from the normal methods, as you can see when you look at the description of the variable tramp-multi-connection-function-alist. (Why isn't that variable named something like tramp-multi-method-alist? Argh. Sorry.) > * and tell users that they *must* specify a `mimencode' or > `uuencode' command for the most remote machine (unless the > connection can automatically default or be auto-dectected). How about a different approach: The user can choose whether multi or multiu is the default multi method. Then, when using a "|" filename without specifying a method, Tramp always uses the default multi method. > Based on this suggestion, my file name would look like the following, > with the `smx' being read only for the SSH part and the `su' telling > Emacs that this is a uuencoding style connection: > > /smx#bob@fencepost.gnu.org|su#bob@titan.berkshire.net:/home/bob/ > > And I could also, equally well, write the file name like this, which > would be more `proper': > > /ssh#bob@fencepost.gnu.org|su#bob@titan.berkshire.net:/home/bob/ I don't think that this approach makes sense because the information in tramp-methods (which lists methods like smx and su) and the information in tramp-multi-connection-function-alist is so dissimilar. Maybe I should have used very different names for the hop methods, such as m1 through m5... kai -- A large number of young women don't trust men with beards. (BFBS Radio)