From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Augusto Stoffel <arstoffel@gmail.com>
Cc: 58049@debbugs.gnu.org
Subject: bug#58049: 29.0.50; Obsolete url schemes "info" and "man"
Date: Sun, 25 Sep 2022 08:09:53 -0700 [thread overview]
Message-ID: <CADwFkm=a2u=Baw4SQRC5G-6e02iWFFARpiy0_MFt367ya_fYBw@mail.gmail.com> (raw)
In-Reply-To: <878rm7bk78.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I'm all for retiring the info: and man: schemes (since they are 100%
> useless), but don't really see the need to do so piecemeal -- when Emacs
> grows a new URL library that functions better than the current one,
> it'll only support http(s) and file, so all this junk will disappear in
> one fell swoop.
I think I agree. Eli also has a point when he says that we might as
well just leave the support in.
How about saying in the URL manual that the info: and man: schemes as
deprecated, so people at least won't try to use them in new code? That
is a small change, but will also potentially make the transition to
something new and improved a tiny bit easier. It'll also discourage
anyone from attempting to re-implement it in the new library.
next prev parent reply other threads:[~2022-09-25 15:09 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
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 [this message]
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='CADwFkm=a2u=Baw4SQRC5G-6e02iWFFARpiy0_MFt367ya_fYBw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=58049@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=larsi@gnus.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).