From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 38713@debbugs.gnu.org
Subject: bug#38713: 27.0.50; eww doesn't handle protocols other than https?
Date: Mon, 23 Dec 2019 00:26:29 +0100 [thread overview]
Message-ID: <87bls0t00q.fsf@gnus.org> (raw)
In-Reply-To: <87pngggdma.fsf@mail.linkov.net> (Juri Linkov's message of "Mon, 23 Dec 2019 01:11:09 +0200")
Juri Linkov <juri@linkov.net> writes:
> 0. emacs -Q
> 1. M-x eww RET about:protocols RET hangs with the following line:
>
> Loading http://about:protocols/...
>
> whereas after applying the following patch it displays the nicely
> formatted HTML page:
>
> Supported Protocols - URL vEmacs
> Protocol Properties Description
> about Synchronous N/A
> Default Port: 0
> ...
I'm not sure that makes much sense, really. Emacs has other ways of
documenting these things other than putting them in an about:
pseudo-protocol thing. (While other browsers do not.)
eww does not support everything that the url* library does, and
shouldn't.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-12-22 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 23:11 bug#38713: 27.0.50; eww doesn't handle protocols other than https? Juri Linkov
2019-12-22 23:26 ` Lars Ingebrigtsen [this message]
2019-12-23 23:12 ` Juri Linkov
2019-12-24 1:31 ` Lars Ingebrigtsen
2020-01-22 16:15 ` Lars Ingebrigtsen
2019-12-24 15:28 ` Eli Zaretskii
2019-12-25 0:36 ` Using eww as browser for Emacs internals and documentation (was: bug#38713: 27.0.50; eww doesn't handle protocols other than https?) Juri Linkov
2019-12-25 21:43 ` Using eww as browser for Emacs internals and documentation Lars Ingebrigtsen
2019-12-25 21:59 ` Juri Linkov
2020-01-08 16:43 ` T.V Raman
2019-12-25 22:22 ` Stefan Monnier
2019-12-25 23:07 ` Lars Ingebrigtsen
2020-01-08 16:44 ` T.V Raman
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=87bls0t00q.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38713@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.