From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Current Tramp plans
Date: 02 Jul 2002 22:10:19 +0200 [thread overview]
Message-ID: <5x65zxgac4.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <vafit44yaw0.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Kai.Grossjohann@cs.uni-dortmund.de (Kai Großjohann) writes:
>
> > Kai.Grossjohann@cs.uni-dortmund.de (Kai Großjohann) writes:
> >
> >> * Then comes an Ange-FTP-like filename format for the non-multi
> >> methods.
> >
> > This is still to do, but ought to be trivial, more or less.
>
> I would like to test things a little bit first. Therefore, I haven't
> made the new setup the default. Instead, people can put
>
> (tramp-handle-ange-ftp)
>
> into their init files to install the new filename format and to turn
> off Ange-FTP. Please test this to see whether you like it.
If I compare this to ange-ftp on a fresh emacs -q, I see two
advanges to ange-ftp over tramp:
1) With tramp, if I enter
C-x C-f //kfs:/ TAB
the input is simply truncated to /. With ange-ftp, I get
completion in the home-directory of / on host `kfs'.
With tramp, I need to enter, e.g. //kfs:/home/ for TAB to work.
2) Tramp does not succeed to connect to the `kfs' host. Ange-ftp
does.
The only method which works for me to connect from this system to
`kfs' is `tu'. The default method used by tramp (rcp) doesn't
work... but there is no indication what is going on.
If at least the echo area would say:
Connecting to `kfs' using `rsh', I'd have a clue to what's up.
Of course, setting tramp-default-method to tu makes everything work
smoothly, but since it doesn't work out-of-the-box like native
ange-ftp does, I don't think the effect of tramp-handle-ange-ftp
should be the default setting. But it is a nice option for tramp
users (and ange-ftp users of course :-).
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-07-02 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 21:08 Current Tramp plans Kai Großjohann
2002-06-21 21:37 ` John Wiegley
2002-06-22 0:07 ` Kim F. Storm
2002-06-21 23:39 ` Miles Bader
2002-06-22 22:51 ` Richard Stallman
2002-06-24 14:07 ` Kai Großjohann
2002-06-24 14:43 ` Kai Großjohann
2002-06-25 11:06 ` Richard Stallman
2002-06-25 20:14 ` Kai Großjohann
2002-06-27 15:55 ` Kai Großjohann
2002-07-02 20:10 ` Kim F. Storm [this message]
2002-07-03 11:11 ` Kai Großjohann
2002-07-09 17:28 ` Kai Großjohann
2002-07-09 20:17 ` Sam Steingold
2002-07-10 8:21 ` Kai Großjohann
2002-07-10 8:29 ` Miles Bader
2002-07-09 20:59 ` Stefan Monnier
2002-07-09 22:10 ` Kim F. Storm
2002-07-10 10:43 ` Richard Stallman
2002-07-11 19:59 ` Kai Großjohann
[not found] <m3wusr1cqu.fsf@totally-fudged-out-message-id>
2002-06-23 15:25 ` Kai Großjohann
2002-06-24 9:33 ` Richard Stallman
2002-06-24 14:12 ` Sam Steingold
2002-06-25 11:06 ` Richard Stallman
[not found] <m3sn3dswp1.fsf@totally-fudged-out-message-id>
2002-06-23 18:11 ` Oliver Scholz
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=5x65zxgac4.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.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).