unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: emacs-devel@gnu.org
Subject: Please post older versions of GNU Emacs manuals on the web
Date: Sat, 2 Jan 2016 08:46:17 -0800 (PST)	[thread overview]
Message-ID: <1e249214-6831-4c2b-98a4-d16a6d1d7048@default> (raw)

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.

(This useful doc _never_ should have been removed from the manual.
But that is not the point of this post.)

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.

Can GNU Emacs not provide its users with the doc for more
than one release on line?  How hard and how costly is that?

In many cases providing this service is maybe not so important,
because Emacs tends to add more than it subtracts (mostly
monotonic).  But in a case such as the wholesale decapitation
of `defadvice' doc you are really out of luck on the web.

Wrt `defadvice', the big concession that was made was to
keep the doc in the Lisp source code, as comments.  That's
piss-poor IMHO, but at least it shows some contrition for
the sin of removing useful doc from users.

How about posting multiple versions of the Emacs doc on line?

---

FWIW, I use a simple command, bound to `G' in Info, to
visit the current Info node on the web.  Sounds silly, but
I use it several times a day, to provide links in answers
I give to online Emacs questions.  (Of course, I also tell
users the preferred method of accessing the doc, `C-h i'.)

(defun Info-goto-node-web (node &optional flip-new-win)
  "Use `browse-url' to go to Info node NODE using a Web browser.
With a prefix arg, reverse the effect of option
option`browse-url-new-window-flag'.

NODE is the name of a node in the GNU Emacs or Elisp manual.
Alternatively, NODE can have the form (MANUAL)NODE, where MANUAL is
\"emacs\" or \"elisp\" and NODE is the name of the node in that
manual.  Empty NODE in (MANUAL) defaults to the `Top' node."
  (interactive
    (list (Info-read-node-name "Go to node: " Info-current-node)
          current-prefix-arg))
  (require 'browse-url)
  (unless Info-current-file
    (error "This command must be invoked from Info"))
  (browse-url (Info-url-for-node node)
              (list (if flip-new-win
                        (not browse-url-new-window-flag)
                      browse-url-new-window-flag))))



             reply	other threads:[~2016-01-02 16:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 16:46 Drew Adams [this message]
2016-01-02 17:01 ` Please post older versions of GNU Emacs manuals on the web 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
     [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=1e249214-6831-4c2b-98a4-d16a6d1d7048@default \
    --to=drew.adams@oracle.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).