GNU bug report logs - #38713
27.0.50; eww doesn't handle protocols other than https?

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: larsi <at> gnus.org, 38713 <at> debbugs.gnu.org
Subject: bug#38713: 27.0.50; eww doesn't handle protocols other than https?
Date: Tue, 24 Dec 2019 17:28:09 +0200

> From: Juri Linkov <juri <at> linkov.net>
> Date: Tue, 24 Dec 2019 01:12:15 +0200
> Cc: 38713 <at> debbugs.gnu.org
> 
> >> 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.)
> 
> This is part of the planned bigger effort - browsers already support
> the 'about' URI scheme, but Emacs is still lagging behind.  I'd like
> to expend lisp/url/url-about.el to give information on Emacs internals
> including about:memory, about:buffers, about:processes, about:timers and
> many more, using HTML instead of semi-obsolete Info or other ad-hoc formats.
> 
> Do you think this is worth the effort?

Can you tell more about the plan?  For example, the following
questions seem to be pertinent:

 . why implement this as part of eww? Emacs is not a browser, which
   can only react to protocols, it has other ways of interaction

 . where will all the HTML content come from? will it be taken from
   the existing documentation or written from scratch?

 . eww is not very sophisticated browser, so are you sure displaying
   HTML with it will be significantly better than "semi-obsolete"
   Info?

 . more generally, what will be the advantages of providing
   documentation this way, as opposed to the way we provide it now?

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.