unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: emacs-pretest-bug@gnu.org, rfrancoise@debian.org
Subject: Re: Tramp 2.0 -> 2.1 migration woes
Date: Mon, 28 Jan 2008 16:32:40 +0100	[thread overview]
Message-ID: <nqbq76ge3r.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <20080128021310.GA3075@Clio.twb.ath.cx> (Trent W. Buck's message of "Mon, 28 Jan 2008 13:13:16 +1100")

"Trent W. Buck" <trentbuck@gmail.com> writes:

>> I also remember some problems in implementation of all these Tramp
>> 2.1 optimizations for the Tramp 2.0 multi-hop paths.
>
> Would it be correct to say that the explicit multi: method was removed
> because other TRAMP changes broke it, and that it will be brought back
> once it's fixed?  Or is it gone for good?  I would (obviously) prefer
> the former.

Nope. The internal data structures have changed significantly, there
is no easy way to get this syntax back. And I'm also not convinced
that this shall be the way to go.

>> On the Tramp todo list, there is the item
>>
>> ;; * WIBNI there was an interactive command prompting for Tramp
>> ;;   method, hostname, username and filename and translates the user
>> ;;   input into the correct filename syntax (depending on the Emacs
>> ;;   flavor) (Reiner Steib)
>>
>> This could be expanded to multi-hops, where it seems to be even more
>> useful. I'll try to find the time to work on it (Threat: I will exploit
>> *you* as tester for this functionality!)
>
> Well, personally I prefer a single complex prompt like
>
>     What path?  /multi:ssh:foo:sudo::
>
> to a long series of simple prompts
>
>     What method? ssh
>     What user [twb]?  RET
>     What host? foo
>     Done [Y/n]? n
>     What method? sudo
>     What user [root]?  RET
>     Done [Y/n]?  RET
>     Filename? /etc/ssh/sshd_config
>
> mainly because I find it easier to copy/paste or M-p
> (previous-history-element) a single prompt than to do it repeatedly
> for several prompts.

Hmm. Then we have conflicting requirements. Reiner's intention was to
guide the novice user ... maybe we need indeed two kinds of interactive
guidance. In your case, something like this could be done:

  Where do you want to go? /sudo:leek: RET
  Which proxy is in front of it? /ssh:twb@leek: RET
  Which proxy is in front of it? /ssh:twb@foo: RET
  Which proxy is in front of it? RET
  Do you want to add it permanently [Y/n]? n RET

  => Added to `tramp-default-proxies-alist' temporarily:
     (("leek" "root" "/ssh:twb@leek:")
      ("leek" "twb"  "/ssh:twb@foo:"))

Best regards, Michael.

  reply	other threads:[~2008-01-28 15:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27  4:00 Tramp 2.0 -> 2.1 migration woes Trent W. Buck
2008-01-27 13:42 ` Michael Albinus
2008-01-28  2:13   ` Trent W. Buck
2008-01-28 15:32     ` Michael Albinus [this message]
2008-01-28 15:57       ` Trent W. Buck
2008-01-28 16:31         ` Michael Albinus
2008-01-29  0:34           ` Trent W. Buck
2008-01-31 11:00             ` Michael Albinus
2008-01-31 14:51               ` Stefan Monnier
2008-01-31 15:46                 ` Michael Albinus
2008-01-27 14:57 ` Michael Albinus
2008-01-28  2:30   ` Trent W. Buck
2008-01-28 14:50     ` Host name for su(do)? (was: Tramp 2.0 -> 2.1 migration woes) Michael Albinus
2008-01-28 15:46       ` Trent W. Buck
2008-01-28 16:10         ` Host name for su(do)? Michael Albinus
2008-01-28 21:47           ` Michael Albinus
2008-01-28 20:54 ` Shell-command is no longer a shell (was: Tramp 2.0 -> 2.1 migration woes) Michael Albinus
2008-01-29  0:43   ` Trent W. Buck
2008-01-29 21:06     ` Shell-command is no longer a shell Michael Albinus
2008-01-31  2:09       ` Trent W. Buck
2008-01-29 20:58 ` sudo -s -H (was: Tramp 2.0 -> 2.1 migration woes) Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nqbq76ge3r.fsf@alcatel-lucent.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=rfrancoise@debian.org \
    --cc=trentbuck@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).