unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, 19822@debbugs.gnu.org, ivan@siamics.net
Subject: bug#19822: url-retrieve: allow to fail when no document is associated with the URI
Date: Mon, 30 Sep 2019 16:40:02 +0200	[thread overview]
Message-ID: <87a7aldf0d.fsf@gnus.org> (raw)
In-Reply-To: <83tv8uchxf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Sep 2019 11:22:20 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> How are network news URL referenced, if not by 'news:'?

They aren't, really.  You use a newsreader to read news -- no modern
browser supports news: URLs.

> Anyway, can we please have an explicit list of those we'd like to
> deprecate, and some usage numbers to back that?  I'd like to have some
> more firm basis for this decision, if possible.

Geez.  Gathering the list of schemes supported is more work than I
thought, because it's not an explicit list.

Here's the schemes it supports:

imap:
file:
http:
https:
ldap:
mail:
mailto:
man:
info:
data:
news:
snews:
nfs:
ftp:
rlogin:
telnet:
tn3270:


Of these, file:, http:, https:, data: and ftp: are the only ones that
are useful.

But on consideration, perhaps it's just best to leave them all as they
are to smoulder.  As you may remember, there's a with-fetched-url branch
that reimplements the entire URL interface, and it only supports the
modern schemes.  (I'm planning on merging when master goes to Emacs 28.)

So we can leave the url.el interfaces alone as a backwards-compatible
stuff and then pension off the entire url.el machinery in, say, Emacs 34.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-09-30 14:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06 19:15 bug#17959: eww: FTP is not supported; but with ftp_proxy, it is Ivan Shmakov
2014-11-04 16:40 ` Ted Zlatanov
2014-11-10 21:20 ` Lars Magne Ingebrigtsen
2014-11-19  8:04   ` Ivan Shmakov
2014-11-19 17:24     ` Lars Magne Ingebrigtsen
2014-12-16 20:09     ` bug#17959: support accessing FTP services via HTTP proxies Ivan Shmakov
2015-01-12 21:40       ` Ivan Shmakov
2015-02-09 16:55         ` bug#19822: url-retrieve: allow to fail when no document is associated with the URI Ivan Shmakov
2015-12-25 19:00           ` Lars Ingebrigtsen
2015-12-28 22:07             ` Ted Zlatanov
     [not found]             ` <87fuym1b2r.fsf@lifelogs.com>
2015-12-28 22:30               ` Lars Ingebrigtsen
     [not found]           ` <87r3iawdyl.fsf@gnus.org>
2015-12-25 23:47             ` Drew Adams
2019-09-30  1:03           ` Stefan Kangas
2019-09-30  5:47             ` Lars Ingebrigtsen
2019-09-30  7:21               ` Eli Zaretskii
2019-09-30  7:30                 ` Lars Ingebrigtsen
2019-09-30  8:22                   ` Eli Zaretskii
2019-09-30 14:40                     ` Lars Ingebrigtsen [this message]
2019-09-30 15:05                       ` Eli Zaretskii
2019-10-01 13:19                       ` Stefan Kangas
2019-10-01 13:37                         ` Eli Zaretskii
2019-10-01 13:44                           ` Stefan Kangas
2019-10-01 14:51                             ` Eli Zaretskii
2019-10-01 15:13                               ` Stefan Kangas
2019-10-01 15:24                                 ` Eli Zaretskii
2019-10-01 13:56                         ` Lars Ingebrigtsen
2019-10-01 14:06                           ` Stefan Kangas
2019-10-01 14:24                             ` Stefan Kangas
2019-10-01 15:13                               ` Lars Ingebrigtsen
2019-10-01 16:07                                 ` Stefan Kangas
2015-02-09 17:04         ` bug#17959: support accessing FTP services via HTTP proxies Ivan Shmakov

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=87a7aldf0d.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=19822@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=ivan@siamics.net \
    --cc=stefan@marxist.se \
    /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).