From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Using eww as browser for Emacs internals and documentation
Date: Wed, 25 Dec 2019 22:43:44 +0100 [thread overview]
Message-ID: <87zhfg2i9b.fsf@gnus.org> (raw)
In-Reply-To: <87mubhduqh.fsf_-_@mail.linkov.net> (Juri Linkov's message of "Wed, 25 Dec 2019 02:36:30 +0200")
Juri Linkov <juri@linkov.net> writes:
> Web browsers support the officially registered URI scheme 'about'
> to reveal internal state and built-in functions:
> https://en.wikipedia.org/wiki/About_URI_scheme
>
> There is one 'about' URI, namely 'about:protocols'
> already implemented in Emacs in lisp/url/url-about.el
> Then why not to support more 'about' URIs like:
>
> about:memory - with data returned from 'garbage-collect'
> about:processes
> about:timers
> about:buffers
> etc.
Web browsers support this sort of thing because that's a nice ad-hoc way
to display data that you don't want to have in the menus.
I don't see why Emacs should emulate that odd approach to hiding
information, especially since Emacs already has commands to display all
this data in a sensible manner. Like I said, `M-x list-timers' will
always be better (for the users) than dumping some data into HTML and
letting shr render it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-12-25 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pngggdma.fsf@mail.linkov.net>
[not found] ` <87bls0t00q.fsf@gnus.org>
[not found] ` <87woammyb4.fsf@mail.linkov.net>
[not found] ` <83lfr1wxo6.fsf@gnu.org>
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 ` Lars Ingebrigtsen [this message]
2019-12-25 21:59 ` Using eww as browser for Emacs internals and documentation 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
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=87zhfg2i9b.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).