unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: John Wiegley <jwiegley@gmail.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:01 -0800 (PST)	[thread overview]
Message-ID: <77dedbec-9cd8-4fca-87d4-219ceb4c9d41@default> (raw)
In-Reply-To: <m27fjr29f7.fsf@newartisans.com>

> > If you have a version of GNU Emacs older than 24.4 then you are lucky to
> > still have `defadvice' documented in the Elisp manual.
> 
> Maybe we should have a "deprecated features" manual, where text gets moved
> after it is removed from the Elisp manual? Even though 25.1 may not use
> defadvice, it still allows such code to be written, which means you'll
> probably run across such code in the future and would like to read
> documentation on how it works.
> 
> I can understand taking it out of the manual, but it would be nice to have
> another manual for "features you may well run into in the wild, though you
> shouldn't write new code this way". I'm not proposing maintaining such a
> manual actively, but just copying deprecated sections like the "defadvice"
> content directly into it instead of deletion.

I'm not against our doing what you suggest (as I say, IMO the `defadvice'
doc should never have been removed from the manual, at least as long as
it is still supported (while deprecated)).

But what I propose is different.  And unlike what you suggest it should
require no extra effort, beyond the one-time effort of building the
HTML doc, which should not be a big deal.

My proposal is for GNU Emacs to post the complete Emacs and Elisp
manuals for older versions.  We could even add a command similar to
what I posted here, which takes the current release into account
when determining the URL.



  reply	other threads:[~2016-01-02 17:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 16:46 Please post older versions of GNU Emacs manuals on the web Drew Adams
2016-01-02 17:01 ` Eli Zaretskii
2016-01-02 17:11 ` John Wiegley
2016-01-02 17:19   ` Drew Adams [this message]
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
     [not found] <<1e249214-6831-4c2b-98a4-d16a6d1d7048@default>
     [not found] ` <<83a8onc3vc.fsf@gnu.org>
2016-01-02 17:19   ` Drew Adams
2016-01-03  6:33     ` Ivan Shmakov
     [not found] ` <<E1aFVL3-0000Fj-8h@fencepost.gnu.org>
2016-01-02 23:16   ` Drew Adams

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=77dedbec-9cd8-4fca-87d4-219ceb4c9d41@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    /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).