From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: URL filename syntax?
Date: Mon, 14 Apr 2003 10:29:07 -0400 [thread overview]
Message-ID: <200304141429.h3EET7t6025961@rum.cs.yale.edu> (raw)
In-Reply-To: 5xk7dxxgov.fsf@kfs2.cua.dk
> > Is it desirable to use URL-like syntax for remote files?
> Summary: No.
I think in the abstract: yes. But since url-handler.el already tries
to do it, you have to be careful not to step on each other's toes.
> For normal find-file syntax, // means to discard everything before the
> second slash; thus, your suggested change may be hard to get through the
> standard read-file-name function (without some changes at the C level).
I think it works OK in practice. You need to provide an appropriate
file-handler for substitute-in-file-name, which is inconvenient
(since you need to re-implement the env-var expansion code), but
it's nothing too bad.
> > I think we can't require our users to type %2F in such cases, and
> > therefore I propose to change the ftp URL syntax to interpret
> > ftp://user@host//foo as the file /foo on the remote host. (And
> > ftp://user@host/foo refers to ~user/foo.)
>
> Again, you are violating the principle that // has a special meaning
> when entering a file name.
But it's only relevant for file-name entry, so the only question is
whether it's going to surprise people and I'd say that as a user
I'd be rather happy to be able to enter a URL even if that means
that I might sometimes need to C-a C-k rather than just appending
the absolute name of the file I'm looking for.
> > * Tramp allows to omit the method. How do I do that with URLs?
You don't. Or you provide a handler for /user@host:/ that turns
the name into a URL, so people can use the old syntax and
it's automatically changed for them.
> /multi://telnet:kai@marvin/su:root@localhost//etc/passwd
> or you would open ~root/etc/passwd, right?
The home dir of the user "root" doesn't have to be "/".
> I definitely prefer the current tramp syntax! It does the job well,
> has a tidy syntax, works well with read-file-name (and ido), and it
> doesn't pretend to be something it ain't.
I can probably agree with the fact that Tramp's syntax is OK and does
the job well. For ange-ftp it's different: the URL syntax is well
established for FTP whereas it's not for ssh and friends.
I like to be able to copy/paste URLs from email and whatnot and open
them in Emacs without having to adjust the name. url-handler.el
serves me "well" except for the fact that it's not too robust.
Stefan
next prev parent reply other threads:[~2003-04-14 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 11:51 URL filename syntax? Kai Großjohann
2003-04-14 15:05 ` Kim F. Storm
2003-04-14 14:29 ` Stefan Monnier [this message]
2003-04-14 19:50 ` Oliver Scholz
2003-04-15 16:26 ` Ehud Karni
2003-04-15 19:19 ` Kai Großjohann
2003-04-15 21:20 ` Ehud Karni
2003-04-17 14:55 ` Kai Großjohann
2003-04-18 2:51 ` Stephen J. Turnbull
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200304141429.h3EET7t6025961@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.