From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56885@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#56885: Fix url-about.el in EWW or make it obsolete
Date: Fri, 05 Aug 2022 08:54:23 +0800 [thread overview]
Message-ID: <8735eb7bnk.fsf@yahoo.com> (raw)
In-Reply-To: <87iln8gkdd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 04 Aug 2022 16:21:18 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>> Why? As I already said, there _is_ a use for it. Is there another way
>> to obtain information about supported URL schemes, their ports,
>> services, and the proxies that apply to them, all in a single page?
>
> If that's something that somebody wants, then writing a new command like
> `url-describe-schemes' (that uses the *Help* machinery) would be the
> natural thing to do.
Why can't we keep what already exists, instead of forcing people to
replace it with something else? That's sounds deliberately annoying to
people.
next prev parent reply other threads:[~2022-08-05 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 12:17 bug#56885: Fix url-about.el in EWW or make it obsolete Stefan Kangas
2022-08-02 12:21 ` Lars Ingebrigtsen
2022-08-04 7:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 8:05 ` Lars Ingebrigtsen
2022-08-04 8:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 8:33 ` Lars Ingebrigtsen
2022-08-04 9:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 9:09 ` Lars Ingebrigtsen
2022-08-04 10:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 14:21 ` Lars Ingebrigtsen
2022-08-05 0:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-05 11:54 ` Lars Ingebrigtsen
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=8735eb7bnk.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56885@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--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).