unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ehud Karni" <ehud@unix.mvs.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: URL filename syntax?
Date: Wed, 16 Apr 2003 00:20:08 +0300	[thread overview]
Message-ID: <200304152120.h3FLK8G1008335@beta.mvs.co.il> (raw)
In-Reply-To: <84y92br2ks.fsf@lucy.is.informatik.uni-duisburg.de> (kai.grossjohann@gmx.net)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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 

> 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.

> (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 (note that the ftp standard is NOT supported).

Ehud.


- -- 
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 mailto:ehud@unix.mvs.co.il                  Better  Safe  Than  Sorry
-----BEGIN PGP SIGNATURE-----
Comment: use http://www.keyserver.net/ to get my key (and others)

iD8DBQE+nHeILFvTvpjqOY0RAg9bAJ9wQ2rouMKFpYZmDPSocYGjKfVkywCeN0Gg
qDz38qBiVxPg+8ZM73MaHVw=
=JCKo
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-04-15 21:20 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 [this message]
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

  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=200304152120.h3FLK8G1008335@beta.mvs.co.il \
    --to=ehud@unix.mvs.co.il \
    --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 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).