* doc/misc/cl.texi (Usage, Installation): Remove outdated information.

This commit is contained in:
Glenn Morris
2010-10-05 19:19:42 -07:00
parent 397ae22618
commit 6003ea5325
2 changed files with 11 additions and 35 deletions

View File

@@ -1,3 +1,7 @@
2010-10-06 Glenn Morris <rgm@gnu.org>
* cl.texi (Usage, Installation): Remove outdated information.
2010-08-26 Michael Albinus <michael.albinus@gmx.de>
Sync with Tramp 2.1.19.

View File

@@ -163,19 +163,6 @@ include at the beginning:
@end example
@noindent
If you want to ensure that the new (Gillespie) version of @dfn{CL}
is the one that is present, add an additional @code{(require 'cl-19)}
call:
@example
(require 'cl)
(require 'cl-19)
@end example
@noindent
The second call will fail (with ``@file{cl-19.el} not found'') if
the old @file{cl.el} package was in use.
It is safe to arrange to load @dfn{CL} at all times, e.g.,
in your @file{.emacs} file. But it's a good idea, for portability,
to @code{(require 'cl)} in your code even if you do this.
@@ -229,29 +216,14 @@ multiple-values feature. @xref{Old CL Compatibility}.
@section Installation
@noindent
Installation of the @dfn{CL} package is simple: Just put the
byte-compiled files @file{cl.elc}, @file{cl-extra.elc},
@file{cl-seq.elc}, @file{cl-macs.elc}, and @file{cl-compat.elc}
into a directory on your @code{load-path}.
The @dfn{CL} package is distributed with Emacs, so there is no need
to install anything.
There are no special requirements to compile this package:
The files do not have to be loaded before they are compiled,
nor do they need to be compiled in any particular order.
You may choose to put the files into your main @file{lisp/}
directory, replacing the original @file{cl.el} file there. Or,
you could put them into a directory that comes before @file{lisp/}
on your @code{load-path} so that the old @file{cl.el} is
effectively hidden.
Also, format the @file{cl.texinfo} file and put the resulting
Info files in the @file{info/} directory or another suitable place.
You may instead wish to leave this package's components all in
their own directory, and then add this directory to your
@code{load-path} and @code{Info-directory-list}.
Add the directory to the front of the list so the old @dfn{CL}
package and its documentation are hidden.
If you do need to install it, just put the byte-compiled files
@file{cl.elc}, @file{cl-extra.elc}, @file{cl-seq.elc},
@file{cl-macs.elc}, and @file{cl-compat.elc} into a directory on your
@code{load-path}. Also, format the @file{cl.texi} file and put the
resulting Info files into a directory in your @code{Info-directory-list}.
@node Naming Conventions, , Installation, Overview
@section Naming Conventions