summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorKarl Heuer <kwzh@gnu.org>1999-07-17 02:23:12 +0000
committerKarl Heuer <kwzh@gnu.org>1999-07-17 02:23:12 +0000
commit08f0f5e9cd19326fb6951448e5ddda4d86b15145 (patch)
tree509de09a0659d357d411ee8930af1f68b0efee13 /lispref
parentb6954afd99c5dedeb4d473c885b78e5453ab5e8c (diff)
downloademacs-08f0f5e9cd19326fb6951448e5ddda4d86b15145.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref')
-rw-r--r--lispref/customize.texi8
-rw-r--r--lispref/files.texi8
-rw-r--r--lispref/keymaps.texi2
-rw-r--r--lispref/nonascii.texi6
4 files changed, 12 insertions, 12 deletions
diff --git a/lispref/customize.texi b/lispref/customize.texi
index b4361076418..51ed4e0d526 100644
--- a/lispref/customize.texi
+++ b/lispref/customize.texi
@@ -385,9 +385,9 @@ You can use the @code{:options} keyword in a hook variable's
the hook; see @ref{Variable Definitions}.
@item alist
-The value must be a list of cons-cells, the car of each cell
-representing a key, and the cdr of the same cell representing and
-associated value. The use can add and a delete key/value pairs, and
+The value must be a list of cons-cells, the @sc{car} of each cell
+representing a key, and the @sc{cdr} of the same cell representing an
+associated value. The user can add and delete key/value pairs, and
edit both the key and the value of each pair.
You can specify the key and value types like this:
@@ -444,7 +444,7 @@ symbol for the key.
:options '("foo" ((function-item some-function) integer) "baz")
@end example
-Many alist uses lists with two elements, instead of cons cells. For
+Many alists use lists with two elements, instead of cons cells. For
example,
@example
diff --git a/lispref/files.texi b/lispref/files.texi
index ac00ba9970c..a94cb2c080e 100644
--- a/lispref/files.texi
+++ b/lispref/files.texi
@@ -113,8 +113,8 @@ It uses an existing buffer if there is one, and otherwise creates a new
buffer and reads the file into it. You may make the buffer current or
display it in a window if you wish, but this function does not do so.
-If @var{wildcards} is non-@code{nil}, which is always true in an
-interactive call, then @code{find-file-noselect} expands wildcard
+If @var{wildcards} is non-@code{nil},
+then @code{find-file-noselect} expands wildcard
characters in @var{filename} and visits all the matching files.
When @code{find-file-noselect} uses an existing buffer, it first
@@ -1925,9 +1925,9 @@ This function returns a list of all versions of the file named
@tindex file-expand-wildcards
@defun file-expand-wildcards pattern &optional full
This function expands the wildcard pattern @var{pattern}, returning
-alist of file names that match it.
+a list of file names that match it.
-If @var{pattern} is written as an absolute relative file name,
+If @var{pattern} is written as an absolute file name,
the values are absolute also.
If @var{pattern} is written as a relative file name, it is interpreted
diff --git a/lispref/keymaps.texi b/lispref/keymaps.texi
index e5cdef59a52..b036679d4f6 100644
--- a/lispref/keymaps.texi
+++ b/lispref/keymaps.texi
@@ -1639,7 +1639,7 @@ to toggle the @code{debug-on-error} flag is defined:
(menu-item "Debug on Error" toggle-debug-on-error
:button (:toggle
. (and (boundp 'debug-on-error)
- debug-on-error))
+ debug-on-error)))
@end example
@noindent
diff --git a/lispref/nonascii.texi b/lispref/nonascii.texi
index 8543a825aa7..7b6745945df 100644
--- a/lispref/nonascii.texi
+++ b/lispref/nonascii.texi
@@ -64,8 +64,8 @@ appear in proper multibyte text (since that consists of a sequence of
In a buffer, the buffer-local value of the variable
@code{enable-multibyte-characters} specifies the representation used.
-The representation for a string is determined when the string is
-constructed and recorded in the string.
+The representation for a string is determined and recorded in the string
+when the string is constructed.
@defvar enable-multibyte-characters
@tindex enable-multibyte-characters
@@ -984,7 +984,7 @@ clean, but raw bytes are used only in limited ways, so as a practical
matter it is not worth the trouble to treat this case differently.
When a multibyte buffer contains illegitimate byte sequences,
-sometimes insertion or deleteion can cause them to coalesce into a
+sometimes insertion or deletion can cause them to coalesce into a
legitimate multibyte character. For example, suppose the buffer
contains the sequence 129 68 192, 68 being the character @samp{D}. If
you delete the @samp{D}, the bytes 129 and 192 become adjacent, and thus