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: Mon, 28 Jan 2008 13:13:16 +1100 [thread overview]
Message-ID: <20080128021310.GA3075@Clio.twb.ath.cx> (raw)
In-Reply-To: <87sl0jxu4g.fsf@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 3176 bytes --]
On Sun, Jan 27, 2008 at 02:42:23PM +0100, Michael Albinus wrote:
>> The initial hops are no longer shown in the path [...]
>> /sudo:root@leek:/etc
>> ...so that instead of editing leek's /etc as root, I was editing my
>> laptop's /etc as root!
>
> That isn't related to multi-hops. It is simply an error in Tramp,
> which shall inform you about the used host.
>
> In case of su(do)?, the host name is ignored (except there is a
> setting in tramp-default-proxies-alist). The Tramp documentation
> says for the su(do)? methods: "... With other words, a specified
> host name in the file name is silently ignored."
>
> Consequently, if you open a file "/sudo:root@leek:/etc", it must be
> expanded to "/sudo:root@localhost:/etc", and this shall be
> visible. A warning (or an error?) shall be raised. I'll fix it.
>
>> It seems that shell-command (M-!) no longer uses a shell in TRAMP
>> Another example was running M-! find -name \*~ -delete RET in
>> /ssh:leek:, which should have deleted backup files in my home
>> directory. In Emacs 22, it behaves correctly. In CVS Emacs, it
>> silently fails.
>
> I'll fix it. Obviously, there was too much optimization in Tramp 2.1 -
> the COMMAND shall still be called via "sh -c COMMAND".
Thanks. These are my two biggest concerns, and I see from your next
message that they're being addressed promptly.
>> Multi-hop now requires tedious alist editing. [details...]
>
> I admit, that in your use case it is a real regression. There have
> been several reasons to change the multi-hop syntax. I remember,
> that for people with *static* multi-hop paths the new syntax is
> shorter and more convenient to type therefore;
Granted. I don't object to adding default proxies.
> 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.
> OTOH, setting up a working tramp-default-proxies-alist is kind of
> complex, indeed.
Agreed.
> 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.
PS: tramp-default-proxies-alist really isn't an alist anymore! :-)
[-- 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 2:13 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 [this message]
2008-01-28 15:32 ` Michael Albinus
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=20080128021310.GA3075@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).