From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: RE: Please post older versions of GNU Emacs manuals on the web
Date: Sat, 2 Jan 2016 09:19:04 -0800 (PST) [thread overview]
Message-ID: <ade8e79f-0675-4bb2-8874-d83a7fa9f395@default> (raw)
In-Reply-To: <<83a8onc3vc.fsf@gnu.org>>
> > Suppose you are using Emacs 24.3 (or Emacs 23 or...). You visit
> > the Elisp manual and you use `i defadvice' to visit the advice doc.
> >
> > You want to visit the same manual section on line (HTTP). Perhaps
> > you want to bookmark it for use when you do not have Emacs available.
> > Or maybe you want to send the URL to someone or post it in online
> > Emacs help. Or maybe you want to print some of the HTML pages.
> >
> > Here's the rub. Only the manuals for the latest Emacs release
> > are available on line. And because Emacs (unwisely) removed the
> > doc for `defadvice', you are out of luck. There is no online doc
> > for you.
>
> Nothing can ever be "removed" from the Internet. You can find your
> v24.3 version of ELisp manual, and in it the chapter about advising,
> here:
>
> https://web.archive.org/web/20121224105042/http://www.gnu.org/software/emacs
> /manual/html_node/elisp/Advising-Functions.html#Advising-Functions
>
> (Google for "wayback machine" if you want to find old versions of some
> URLs, including URLs that no longer exist.)
Sure, the Wayback Machine is a great resource, and the Internet
Archive responsible for it is a great place to visit in San Francisco.
But telling users to look to Internet archives (or to just google for
"defadvice emacs") does not really answer my question of "Why not?"
or respond to my proposal.
IMO we should offer Emacs users easy online access to the manuals for
older Emacs versions, the same way we offer them easy access to the
recent manuals and to both the recent and older versions of the software.
This is the least we could do to help users and show them respect.
It should not be easier to find information about older releases of
Oracle, Apple, Microsoft, or IBM software than it is to find such
info for Emacs.
next parent reply other threads:[~2016-01-02 17:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1e249214-6831-4c2b-98a4-d16a6d1d7048@default>
[not found] ` <<83a8onc3vc.fsf@gnu.org>
2016-01-02 17:19 ` Drew Adams [this message]
2016-01-03 6:33 ` Please post older versions of GNU Emacs manuals on the web Ivan Shmakov
[not found] ` <<E1aFVL3-0000Fj-8h@fencepost.gnu.org>
2016-01-02 23:16 ` Drew Adams
2016-01-02 16:46 Drew Adams
2016-01-02 17:01 ` Eli Zaretskii
2016-01-02 17:11 ` John Wiegley
2016-01-02 17:19 ` Drew Adams
2016-01-04 3:15 ` Richard Stallman
2016-01-02 23:11 ` Richard Stallman
2016-01-03 3:57 ` John Wiegley
2016-01-03 4:09 ` Drew Adams
2016-01-03 4:18 ` raman
2016-01-03 10:55 ` David Kastrup
2016-01-03 16:34 ` Drew Adams
2016-01-03 2:07 ` Xue Fuqiao
2016-01-03 3:14 ` raman
2016-01-03 3:32 ` Drew Adams
2016-01-03 7:08 ` Teemu Likonen
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=ade8e79f-0675-4bb2-8874-d83a7fa9f395@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--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).