unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: URL filename syntax?
Date: Thu, 17 Apr 2003 16:55:24 +0200	[thread overview]
Message-ID: <848yu9p40z.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 200304152120.h3FLK8G1008335@beta.mvs.co.il

"Ehud Karni" <ehud@unix.mvs.co.il> writes:

> On Tue, 15 Apr 2003 21:19:15 +0200, kai.grossjohann@gmx.net (Kai =?iso-8859-1?q?Gro=DFjohann?=) wrote:
>> 
>> Are you talking about my suggestion of changing ftp://user@host//foo
>> to mean the same as ftp://user@host/%2Ffoo, instead of
>> ftp://user@host/foo?
>
> No. I'm talking about the general principal - any legal URL should work
> without modification. If `wget' can transfer it, Emacs should be able
> to edit it in a buffer (It may be read only).
> e.g. https://www.name.tld/foo/bar.html 

Maybe Tramp does not support http and https URLs initially.

>> It's not quite clear what you want:
>> 
>> (a) ftp://user@host/%2Ffoo must have the standard meaning, or
>> (b) ftp://user@host//foo must have the standard meaning (ie, same as
>>     ftp://user@host/foo), or
>> (c) both.
>> 
>> I agree on (a).  But for (b) I'd say the added convenience outweighs
>> the slight incompatibility with the standard.
>
> (a) must be supported (any legal URL should work).
> (b) MAY be supported - improvements are welcomed.

Okay.  It seems that ftp://user@host//foo is an illegal URL, so I can
assign any meaning to it that I like.  Hence, I'll define it to mean
the same thing as ftp://user@host/%2Ffoo.

Do you object?

>> (And Tramp is incompatible with the standard anyway, since it mostly
>> supports URL schemes like ssh, scp, su, smb, and rsync, which are not
>> standardized.)
>
> If there is no standard - there is no incompatibility.
> If there will be standard for any of these methods - it should be
> supported

Yes.

Though I am afraid that there might be a standard which defines some
completely useless meaning to these URLs from Tramp's point of view.
For example, if there is ever a standard that says that
ssh://user@host/ should open a terminal window, then Tramp can't
meaningfully support it.  (Tramp will show a dired buffer of the home
dir of that user on that host instead.)

> (note that the ftp standard is NOT supported).

The ftp standard is not supported by whom?

Tramp does not currently use URL-like syntax, but it does support ftp
(on Emacs, via Ange-FTP).
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

  reply	other threads:[~2003-04-17 14:55 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
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 [this message]
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

  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=848yu9p40z.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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).