From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp/Ange-FTP filename unification
Date: 12 Jul 2002 18:15:35 +0900 [thread overview]
Message-ID: <buo4rf5s3wo.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <vafvg7l48tf.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> >> /method:user@host:/path/to/file
> >
> > Using `:' for both separators makes filenames with omitted components
> > more ambiguous.
>
> Well, the filename "/method:/path/to/file" does not make sense IMHO.
> Tramp is for editing remote files, you should always specify at least
> a host name. So in a filename like "/x:y", the x will be interpreted
> as a host name.
What about methods that just su? There doesn't seem to be any reason
why tramp should be only for remote files; it's really a way of editing
through a shell connection, with remote shells being a particularly
common and handy subset of that functionality.
> Do you think that's bad?
Well, I think that it's good that X in `/X:Y' will be interpreted as a
hostname, but it seems desirable to be able to specify a `method-only'
name for methods where a hostname doesn't make any sense.
Maybe `:' _is_ the right choice, and something like `/M::P' should be
required for method-only names, but I think it deserves some discussion.
-Miles
--
97% of everything is grunge
next prev parent reply other threads:[~2002-07-12 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 20:43 Tramp/Ange-FTP filename unification Kai Großjohann
2002-07-12 0:48 ` Miles Bader
2002-07-12 9:03 ` Kai Großjohann
2002-07-12 9:15 ` Miles Bader [this message]
2002-07-12 9:47 ` Kai Großjohann
2002-07-12 12:40 ` Kim F. Storm
2002-07-12 13:09 ` Kai Großjohann
2002-07-12 14:28 ` Juanma Barranquero
2002-07-12 15:34 ` Kim F. Storm
2002-07-12 14:45 ` Juanma Barranquero
2002-07-12 23:22 ` Kim F. Storm
2002-07-13 3:24 ` Juanma Barranquero
2002-07-13 0:51 ` Kim F. Storm
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=buo4rf5s3wo.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@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).