From: storm@cua.dk (Kim F. Storm)
Cc: Miles Bader <miles@gnu.org>, emacs-devel@gnu.org
Subject: Re: Tramp/Ange-FTP filename unification
Date: 12 Jul 2002 14:40:27 +0200 [thread overview]
Message-ID: <5xk7o1unk4.fsf@kfs2.cua.dk> (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:
> Miles Bader <miles@lsi.nec.co.jp> writes:
>
> > Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> >> I think I've now done it so that it works. The new filename format
> >> is this:
> >>
> >> Normal:
> >> /method:user@host:/path/to/file
> >> Multi-hop:
> >> /multi:hopm1:user1@host1:hopm2:user2@host2:/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.
>
> Do you think that's bad?
Like Miles, I was worried at first, but I think the new syntax makes sense.
In any case, the "long style syntax" wouldn't really matter if tramp
handles "host abbrevs" so that writing /xyz:/ is automagically
expanded to /multi:m1:u1@h1:m2:u2@u2:/ (behind the scenes please)
whenever it is used.
This will also allow me to make an abbrev /su:/ to do "su root" on my
own machine by expanding to /su:root@localhost:/.
So is tramp-abbrevs implemented yet?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-07-12 12:40 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
2002-07-12 9:47 ` Kai Großjohann
2002-07-12 12:40 ` Kim F. Storm [this message]
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=5xk7o1unk4.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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).