From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Current Tramp plans
Date: Fri, 21 Jun 2002 23:08:38 +0200 [thread overview]
Message-ID: <vafznxo49wp.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
There has been a lot of discussion regarding Tramp. I would like to
thank all participants for their thoughtful comments.
My summary of the situation:
* The longterm goal is to unify the Tramp and Ange-FTP filenames, and
to use a format for the filenames which is a superset of the
Ange-FTP format.
* The Ange-FTP entries are deleted from file-name-handler-alist.
* In certain cases, Tramp forwards the file operations to Ange-FTP.
These cases include:
- ftp is explicitly mentioned in the filename
- the user has said to always use ftp for certain user/host
combinations
Additionally, we might want to default to ftp in some cases, such
as when the user is anonymous.
* Different people have different opinions on what the new format
should look like. Proposals for the non-multi case that seem to be
still in the competition:
Richard:
/user@host@method:file
empty strings for omitted/defaulted components, eg
/@host@method:file
Miles (?)
/user@host#method:file
numeric methods would be considered ports for ftp
Kai:
/[method]user@host:file
Because I really doubt that square brackets in the user
name are actually needed.
And if they are needed, people can just say something like
/[sm][xx]yy@zz:file
This will use the sm method, connect to host zz, and use
the user name "[xx]yy".
Since square brackets are quite rare, I don't think
it matters that people have to type a slightly longer
filename in this case.
/method#user@host:file
because `#' is already used by Ange-FTP as a special character
If there is more than one colon before the first slash, then we
know that it must be a multi-hop method. Hence, the colon can be
reused as a separator between hops.
I would like to proceed in a step-by-step fashion:
* First, I want to make it so that Tramp can forward requests to
Ange-FTP.
* Then I need to have Tramp accept the port number for the Ange-FTP
case.
* Then comes an Ange-FTP-like filename format for the non-multi
methods.
* Then comes a new format for the multi-hop filenames.
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
next reply other threads:[~2002-06-21 21:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 21:08 Kai Großjohann [this message]
2002-06-21 21:37 ` Current Tramp plans 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
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=vafznxo49wp.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).