diff options
| author | Karl Heuer | 1999-07-17 02:23:12 +0000 |
|---|---|---|
| committer | Karl Heuer | 1999-07-17 02:23:12 +0000 |
| commit | 08f0f5e9cd19326fb6951448e5ddda4d86b15145 (patch) | |
| tree | 509de09a0659d357d411ee8930af1f68b0efee13 | |
| parent | b6954afd99c5dedeb4d473c885b78e5453ab5e8c (diff) | |
| download | emacs-08f0f5e9cd19326fb6951448e5ddda4d86b15145.tar.gz emacs-08f0f5e9cd19326fb6951448e5ddda4d86b15145.zip | |
*** empty log message ***
| -rw-r--r-- | lispref/customize.texi | 8 | ||||
| -rw-r--r-- | lispref/files.texi | 8 | ||||
| -rw-r--r-- | lispref/keymaps.texi | 2 | ||||
| -rw-r--r-- | lispref/nonascii.texi | 6 |
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 | |||
| 385 | the hook; see @ref{Variable Definitions}. | 385 | the hook; see @ref{Variable Definitions}. |
| 386 | 386 | ||
| 387 | @item alist | 387 | @item alist |
| 388 | The value must be a list of cons-cells, the car of each cell | 388 | The value must be a list of cons-cells, the @sc{car} of each cell |
| 389 | representing a key, and the cdr of the same cell representing and | 389 | representing a key, and the @sc{cdr} of the same cell representing an |
| 390 | associated value. The use can add and a delete key/value pairs, and | 390 | associated value. The user can add and delete key/value pairs, and |
| 391 | edit both the key and the value of each pair. | 391 | edit both the key and the value of each pair. |
| 392 | 392 | ||
| 393 | You can specify the key and value types like this: | 393 | You can specify the key and value types like this: |
| @@ -444,7 +444,7 @@ symbol for the key. | |||
| 444 | :options '("foo" ((function-item some-function) integer) "baz") | 444 | :options '("foo" ((function-item some-function) integer) "baz") |
| 445 | @end example | 445 | @end example |
| 446 | 446 | ||
| 447 | Many alist uses lists with two elements, instead of cons cells. For | 447 | Many alists use lists with two elements, instead of cons cells. For |
| 448 | example, | 448 | example, |
| 449 | 449 | ||
| 450 | @example | 450 | @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 | |||
| 113 | buffer and reads the file into it. You may make the buffer current or | 113 | buffer and reads the file into it. You may make the buffer current or |
| 114 | display it in a window if you wish, but this function does not do so. | 114 | display it in a window if you wish, but this function does not do so. |
| 115 | 115 | ||
| 116 | If @var{wildcards} is non-@code{nil}, which is always true in an | 116 | If @var{wildcards} is non-@code{nil}, |
| 117 | interactive call, then @code{find-file-noselect} expands wildcard | 117 | then @code{find-file-noselect} expands wildcard |
| 118 | characters in @var{filename} and visits all the matching files. | 118 | characters in @var{filename} and visits all the matching files. |
| 119 | 119 | ||
| 120 | When @code{find-file-noselect} uses an existing buffer, it first | 120 | 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 | |||
| 1925 | @tindex file-expand-wildcards | 1925 | @tindex file-expand-wildcards |
| 1926 | @defun file-expand-wildcards pattern &optional full | 1926 | @defun file-expand-wildcards pattern &optional full |
| 1927 | This function expands the wildcard pattern @var{pattern}, returning | 1927 | This function expands the wildcard pattern @var{pattern}, returning |
| 1928 | alist of file names that match it. | 1928 | a list of file names that match it. |
| 1929 | 1929 | ||
| 1930 | If @var{pattern} is written as an absolute relative file name, | 1930 | If @var{pattern} is written as an absolute file name, |
| 1931 | the values are absolute also. | 1931 | the values are absolute also. |
| 1932 | 1932 | ||
| 1933 | If @var{pattern} is written as a relative file name, it is interpreted | 1933 | 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: | |||
| 1639 | (menu-item "Debug on Error" toggle-debug-on-error | 1639 | (menu-item "Debug on Error" toggle-debug-on-error |
| 1640 | :button (:toggle | 1640 | :button (:toggle |
| 1641 | . (and (boundp 'debug-on-error) | 1641 | . (and (boundp 'debug-on-error) |
| 1642 | debug-on-error)) | 1642 | debug-on-error))) |
| 1643 | @end example | 1643 | @end example |
| 1644 | 1644 | ||
| 1645 | @noindent | 1645 | @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 | |||
| 64 | 64 | ||
| 65 | In a buffer, the buffer-local value of the variable | 65 | In a buffer, the buffer-local value of the variable |
| 66 | @code{enable-multibyte-characters} specifies the representation used. | 66 | @code{enable-multibyte-characters} specifies the representation used. |
| 67 | The representation for a string is determined when the string is | 67 | The representation for a string is determined and recorded in the string |
| 68 | constructed and recorded in the string. | 68 | when the string is constructed. |
| 69 | 69 | ||
| 70 | @defvar enable-multibyte-characters | 70 | @defvar enable-multibyte-characters |
| 71 | @tindex enable-multibyte-characters | 71 | @tindex enable-multibyte-characters |
| @@ -984,7 +984,7 @@ clean, but raw bytes are used only in limited ways, so as a practical | |||
| 984 | matter it is not worth the trouble to treat this case differently. | 984 | matter it is not worth the trouble to treat this case differently. |
| 985 | 985 | ||
| 986 | When a multibyte buffer contains illegitimate byte sequences, | 986 | When a multibyte buffer contains illegitimate byte sequences, |
| 987 | sometimes insertion or deleteion can cause them to coalesce into a | 987 | sometimes insertion or deletion can cause them to coalesce into a |
| 988 | legitimate multibyte character. For example, suppose the buffer | 988 | legitimate multibyte character. For example, suppose the buffer |
| 989 | contains the sequence 129 68 192, 68 being the character @samp{D}. If | 989 | contains the sequence 129 68 192, 68 being the character @samp{D}. If |
| 990 | you delete the @samp{D}, the bytes 129 and 192 become adjacent, and thus | 990 | you delete the @samp{D}, the bytes 129 and 192 become adjacent, and thus |