all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 56885@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#56885: Fix url-about.el in EWW or make it obsolete
Date: Thu, 04 Aug 2022 16:21:18 +0200	[thread overview]
Message-ID: <87iln8gkdd.fsf@gnus.org> (raw)
In-Reply-To: <875yj88fyz.fsf@yahoo.com> (Po Lu's message of "Thu, 04 Aug 2022 18:23:32 +0800")

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.  I haven't really seen anybody (else) request that,
though.






  reply	other threads:[~2022-08-04 14:21 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 [this message]
2022-08-05  0:54                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iln8gkdd.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56885@debbugs.gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.