From: "Trent W. Buck" <trentbuck@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-pretest-bug@gnu.org, rfrancoise@debian.org
Subject: Re: Tramp 2.0 -> 2.1 migration woes
Date: Tue, 29 Jan 2008 02:57:12 +1100 [thread overview]
Message-ID: <20080128155710.GB2378@Clio.twb.ath.cx> (raw)
In-Reply-To: <nqbq76ge3r.fsf@alcatel-lucent.de>
[-- Attachment #1.1: Type: text/plain, Size: 2149 bytes --]
On Mon, Jan 28, 2008 at 04:32:40PM +0100, Michael Albinus wrote:
>> 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.
Darn. Whenever I get used to something it goes and changes on me :-)
> > Well, personally I prefer a single complex prompt like [...] to a
> > long series of simple prompts [...] 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:"))
I think I could learn to tolerate that amount of prompting... one
thing to consider is what happens if I mess up the multihop (proxy)
sequence because e.g. the notes the other sysadmin gave me are out of
date. Would I have to manually remove the entries from
tramp-default-proxies-alist?
I'm also not sure that middling to complicated proxying arrangements
can even be set up with the current tramp-default-proxies-alist. For
example, suppose a host allows ssh from anywhere, but locks down its
internal staff-only FTP upload area to sites on the corporate subnet?
You'd need to have the /ftp:appdev:/incoming use an /ssh:gw: proxy,
but /ssh:appdev: should not use any proxy (although it would still
work with one, it would just waste gw's bandwidth).
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2008-01-28 15:57 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
2008-01-28 15:57 ` Trent W. Buck [this message]
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=20080128155710.GB2378@Clio.twb.ath.cx \
--to=trentbuck@gmail.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rfrancoise@debian.org \
/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).