From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58049@debbugs.gnu.org
Subject: bug#58049: 29.0.50; Obsolete url schemes "info" and "man"
Date: Sun, 25 Sep 2022 07:57:46 +0300 [thread overview]
Message-ID: <83r100m4ol.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=j0Nqd7svdTuuOK1Wjy0O6Oas076SSyrnRoXgLLGQsMQ@mail.gmail.com> (message from Stefan Kangas on Sat, 24 Sep 2022 19:05:13 -0400)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 24 Sep 2022 19:05:13 -0400
>
> Severity: wishlist
>
> I don't think non-standard URLs like these are used much, and they're
> probably not very useful. They're more likely to cause confusion.
How do you know all these things? Do you have any data to support
those opinions?
> (url-retrieve-synchronously "info:url#Retrieving URLs")
> (url-retrieve-synchronously "man:cat")
>
> I suggest support for such URLs is obsoleted, and that they are removed
> from (info "(url) Supported URL Types").
I don't see why we should. Do they require any significant
maintenance effort to keep them?
Let's not obsolete/remove features just because we don't know who'd
need them. Support for many features, some of them perhaps obscure to
many, is one of important traits of Emacs, so let's try keeping that
where it costs us little to do so.
next prev parent reply other threads:[~2022-09-25 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 23:05 bug#58049: 29.0.50; Obsolete url schemes "info" and "man" Stefan Kangas
2022-09-25 4:57 ` Eli Zaretskii [this message]
2022-09-25 11:52 ` Jean Louis
2022-09-25 14:01 ` Augusto Stoffel
2022-09-25 14:06 ` Augusto Stoffel
2022-09-25 14:30 ` Lars Ingebrigtsen
2022-09-25 14:41 ` Eli Zaretskii
2022-09-25 14:46 ` Lars Ingebrigtsen
2022-09-25 15:09 ` Stefan Kangas
2022-09-26 10:51 ` Lars Ingebrigtsen
2022-09-26 11:15 ` Stefan Kangas
2022-09-27 6:00 ` Jean Louis
2022-09-27 18:02 ` Stefan Kangas
2022-09-27 20:23 ` Jean Louis
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=83r100m4ol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58049@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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).