From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: larsi@gnus.org, 19822@debbugs.gnu.org, ivan@siamics.net
Subject: bug#19822: url-retrieve: allow to fail when no document is associated with the URI
Date: Tue, 01 Oct 2019 17:51:49 +0300 [thread overview]
Message-ID: <83ftkca58b.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmjDS5FkHJqYVsC5i+=Xm+j8R8j3jcfYVa4o4SXqpQ0XA@mail.gmail.com> (message from Stefan Kangas on Tue, 1 Oct 2019 15:44:15 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 1 Oct 2019 15:44:15 +0200
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 19822@debbugs.gnu.org, Ivan Shmakov <ivan@siamics.net>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > I don't feel very strongly about this, but I'm curious: Why don't you
> > > want to obsolete at least some of them? I think they add user
> > > confusion and are just not very helpful.
> >
> > How would obsoleting them help avoid that confusion?
>
> I think in at least two ways:
>
> 1. Obsoleting is a fairly strong sign that this is code that it's
> probably better to avoid.
>
> 2. AFAIU, the point of obsoleting a file is to eventually remove it.
> If it doesn't exist, it can't confuse anyone.
I understand how removing will end the confusion. What I don't quite
understand is how obsoleting will help avoiding the confusion. I
think the obsolete messages just add to the confusion, not take away.
Lars suggested to let this stuff become fallback, which means users
will see the confusing stuff much less frequently. That made sense to
me.
next prev parent reply other threads:[~2019-10-01 14:51 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
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 [this message]
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=83ftkca58b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19822@debbugs.gnu.org \
--cc=ivan@siamics.net \
--cc=larsi@gnus.org \
--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).