From: Richard Stallman <rms@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Referring users to external web pages
Date: Fri, 20 Jan 2017 15:56:38 -0500 [thread overview]
Message-ID: <E1cUgEg-0008HQ-G8@fencepost.gnu.org> (raw)
In-Reply-To: <247147c8-d213-0e2b-5b5f-70d6e0aea799@gmail.com> (message from Clément Pit--Claudel on Thu, 19 Jan 2017 18:34:18 -0500)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > As far as I know there's no commonly-installed, free CSS documentation.
> > Normally I'd write this code to look for an installed copy first, but I
> > don't think there's one to look for.
> I wonder how easy it would be to repackage MDN's documentation as an info manual.
Repackaging it is not necessary in order to have a local copy.
You could have a local copy of exactly what's on their web site.
So I'm saying that the Emacs code to access the documentation
should make provision to access a local copy if there is one.
Any repackaging is not part of Emacs's responsibility, but this
part is.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
prev parent reply other threads:[~2017-01-20 20:56 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
2017-01-20 17:21 ` Tom Tromey
2017-01-20 20:56 ` Richard Stallman [this message]
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=E1cUgEg-0008HQ-G8@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
/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).