summaryrefslogtreecommitdiff
path: root/lispintro
diff options
context:
space:
mode:
authorRobert J. Chassell <bob@rattlesnake.com>2006-10-31 18:07:16 +0000
committerRobert J. Chassell <bob@rattlesnake.com>2006-10-31 18:07:16 +0000
commitb096c3a92d0b7c38f6ab44ecb389d533a10c2ee9 (patch)
tree3d0f0a40433d7f5d414abb5ccbed9e9acb031d2e /lispintro
parent6c850af4a10e64f86433e554c801cbe3fcd337d1 (diff)
downloademacs-b096c3a92d0b7c38f6ab44ecb389d533a10c2ee9.tar.gz
* emacs-lisp-intro.texi: Remove version reference for X colors.
Document `='. Remove mention that :eval was new in 21. Updated instance's edition-number to 3.01.
Diffstat (limited to 'lispintro')
-rw-r--r--lispintro/ChangeLog6
-rw-r--r--lispintro/emacs-lisp-intro.texi36
2 files changed, 20 insertions, 22 deletions
diff --git a/lispintro/ChangeLog b/lispintro/ChangeLog
index bc9a128b1b9..324a5f6c746 100644
--- a/lispintro/ChangeLog
+++ b/lispintro/ChangeLog
@@ -7,7 +7,11 @@
now irrelevant. Updated Info file in ../info. Changed numbering
so is now Revised Third Edition and this instance's edition-number
is 3.00. Did not update ISBN number.
-
+
+ * emacs-lisp-intro.texi: Remove version reference for X colors.
+ Document `='. Remove mention that :eval was new in 21. Updated
+ instance's edition-number to 3.01.
+
2006-10-30 Robert J. Chassell <bob@rattlesnake.com>
* emacs-lisp-intro.texi: Many changes since it turned out that
diff --git a/lispintro/emacs-lisp-intro.texi b/lispintro/emacs-lisp-intro.texi
index 6d1f9bf88fe..77d2252b671 100644
--- a/lispintro/emacs-lisp-intro.texi
+++ b/lispintro/emacs-lisp-intro.texi
@@ -24,7 +24,7 @@
@comment %**end of header
-@set edition-number 3.00
+@set edition-number 3.01
@set update-date 2006 Oct 31
@ignore
@@ -731,7 +731,7 @@ Your @file{.emacs} File
* Loading Files:: Load (i.e., evaluate) files automatically.
* Autoload:: Make functions available.
* Simple Extension:: Define a function; bind it to a key.
-* X11 Colors:: Colors in version 19 in X.
+* X11 Colors:: Colors in X.
* Miscellaneous::
* Mode Line:: How to customize your mode line.
@@ -4526,6 +4526,10 @@ tests whether the first argument is less than or equal to the second and
the second. In all cases, both arguments must be numbers or markers
(markers indicate positions in buffers).
+@item =
+The @code{=} function tests whether two arguments, , both numbers or
+markers, are equal.
+
@item string<
@itemx string-lessp
@itemx string=
@@ -15730,15 +15734,6 @@ nil
@end group
@end smallexample
-@ignore
-(directory-files-and-attributes "/usr/local/src/emacs/lisp/mail/") -->
-(("." t 3 1000 100 (17733 1296) (17718 8756) (17718 8756) 4096 "drwxr-xr-x" nil 1273504 773))
-
-(directory-files-and-attributes "/usr/local/src/emacs/lisp/") -->
-(... ("mail" t 3 1000 100 (17733 1296) (17718 8756) (17718 8756) 4096
-"drwxr-xr-x" nil 1273504 773) ...)
-@end ignore
-
@need 1200
On the other hand, @file{mail/} is a directory within the @file{lisp/}
directory. The beginning of its listing looks like this:
@@ -17172,8 +17167,8 @@ initialization file, which is usually called @file{.emacs}.
I myself use @code{customize} for hardly anything. Mostly, I write
expressions myself.
-@findex defsubst
-@findex defconst
+@findex defsubst
+@findex defconst
Incidentally, @code{defsubst} defines an inline function. The syntax
is just like that of @code{defun}. @code{defconst} defines a symbol
as a constant. The intent is that neither programs nor users should
@@ -18308,13 +18303,12 @@ this number. (Buffer names can and often should be longer than 12
characters; this length works well in a typical 80 column wide
window.)
-@code{:eval} was a new feature in GNU Emacs version 21. It says to
-evaluate the following form and use the result as a string to display.
-In this case, the expression displays the first component of the full
-system name. The end of the first component is a @samp{.} (`period'),
-so I use the @code{string-match} function to tell me the length of the
-first component. The substring from the zeroth character to that
-length is the name of the machine.
+@code{:eval} says to evaluate the following form and use the result as
+a string to display. In this case, the expression displays the first
+component of the full system name. The end of the first component is
+a @samp{.} (`period'), so I use the @code{string-match} function to
+tell me the length of the first component. The substring from the
+zeroth character to that length is the name of the machine.
@need 1250
This is the expression:
@@ -19491,7 +19485,7 @@ element.
Incidentally, both @code{kill-ring} and @code{kill-ring-yank-pointer}
are @dfn{global variables}. That means that any expression in Emacs
Lisp can access them. They are not like the local variables set by
-@code{let} or like the symbols in an argument list.
+@code{let} or like the symbols in an argument list.
Local variables can only be accessed
within the @code{let} that defines them or the function that specifies
them in an argument list (and within expressions called by them).