From: Yuri Khan <yuri.v.khan@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Referring users to external web pages
Date: Sat, 21 Jan 2017 00:09:04 +0700 [thread overview]
Message-ID: <CAP_d_8VRMSP2CLKHqn1X7iiS0K4Y9g+p1suc2Kr=n__df3QZKA@mail.gmail.com> (raw)
In-Reply-To: <jwvk29pwvjq.fsf-monnier+gmane.emacs.devel@gnu.org>
On Fri, Jan 20, 2017 at 11:24 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> I wonder how easy it would be to repackage MDN's documentation as an
>> info manual.
>
> An easier first step might be to make sure that those Mozilla pages get
> cached locally after you access them, with a fairly long "time before
> refresh" (and in such a way that subsequent accesses don't need *any*
> network access).
I really dislike both of the above ideas.
MDN is a wiki. That means anybody* could add useful information at any
time. Both repackaging in a different format and caching aggressively
will defeat that advantage. It will also discourage or prevent the
user from participating.
Additionally, some MDN articles contain live examples which will only
make sense in a fairly capable web browser.
I would certainly appreciate being able to jump to a relevant MDN
article by pressing an easy key in Emacs, but I would prefer reading
it in my preferred browser.
*) Anybody who is not averse to having a Github account.
next prev parent reply other threads:[~2017-01-20 17:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 17:48 Referring users to external web pages Simen Heggestøyl
2017-01-19 3:53 ` John Wiegley
2017-01-19 22:43 ` Richard Stallman
2017-01-19 23:05 ` Tom Tromey
2017-01-19 23:34 ` Clément Pit--Claudel
2017-01-20 6:54 ` Marcin Borkowski
2017-01-20 16:24 ` Stefan Monnier
2017-01-20 17:09 ` Yuri Khan [this message]
2017-01-20 17:21 ` Tom Tromey
2017-01-20 20:56 ` Richard Stallman
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='CAP_d_8VRMSP2CLKHqn1X7iiS0K4Y9g+p1suc2Kr=n__df3QZKA@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.