1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
--- elisp-orig/display.texi 1990-10-11 00:14:05.000000000 +0000
+++ elisp/display.texi 2008-11-25 23:01:58.000000000 +0000
@@ -484,5 +484,5 @@
@quotation
-@strong{Note:} in version 18, this function is named
+@strong{Please note:} in version 18, this function is named
@code{blink-paren-hook}, but since it is not called with the standard
convention for hooks, it is being renamed to @code{blink-paren-function}
--- elisp-orig/elisp.texi 1990-12-05 20:49:07.000000000 +0000
+++ elisp/elisp.texi 2008-11-25 23:01:58.000000000 +0000
@@ -112,5 +112,5 @@
@page
-@node Top, Introduction, (dir), (dir)
+@node Top, License, (dir), (dir)
@ifinfo
--- elisp-orig/files.texi 1990-06-26 13:54:44.000000000 +0000
+++ elisp/files.texi 2008-11-25 23:01:58.000000000 +0000
@@ -189,6 +189,6 @@
appended to get an unused name. See also @ref{Creating Buffers}.
-@strong{Note:} @code{create-file-buffer} does @emph{not} associate the
-new buffer with a file and does not make it the current buffer.
+@strong{Please note:} @code{create-file-buffer} does @emph{not} associate
+the new buffer with a file and does not make it the current buffer.
@example
--- elisp-orig/help.texi 1990-05-31 18:50:37.000000000 +0000
+++ elisp/help.texi 2008-11-25 23:01:58.000000000 +0000
@@ -252,6 +252,6 @@
@end table
-@strong{Note:} each @samp{\} must be doubled when written in a string in
-Emacs Lisp.
+@strong{Please note:} each @samp{\} must be doubled when written in a
+string in Emacs Lisp.
Here are examples of the special substrings:
--- elisp-orig/hooks.texi 1990-05-16 15:39:45.000000000 +0000
+++ elisp/hooks.texi 2008-11-25 23:01:58.000000000 +0000
@@ -12,5 +12,5 @@
@quotation
-@strong{Note:} in version 19, @code{blink-paren-hook} and
+@strong{Please note:} in version 19, @code{blink-paren-hook} and
@code{auto-fill-hook} are renamed to @code{blink-paren-function} and
@code{auto-fill-function} respectively, since they are not called by the
--- elisp-orig/markers.texi 1990-05-31 19:10:17.000000000 +0000
+++ elisp/markers.texi 2008-11-25 23:01:58.000000000 +0000
@@ -364,6 +364,6 @@
The old value of the mark is @emph{not} pushed onto the mark ring.
- @strong{Note:} use this function only if you want the user to see that
-the mark has moved, and you want the previous mark position to be lost.
+ @strong{Please note:} use this function only if you want the user to see
+that the mark has moved, and you want the previous mark position to be lost.
Normally, when a new mark is set, the old one should go on the
@code{mark-ring}, which is why most applications should use
--- elisp-orig/os.texi 1990-11-29 23:02:02.000000000 +0000
+++ elisp/os.texi 2008-11-25 23:01:58.000000000 +0000
@@ -90,5 +90,5 @@
@end defopt
-@node Init File, Terminal-Specific, Start-Up Summary, Starting Up
+@node Init File, Terminal-Specific, Start-up Summary, Starting Up
@subsection The Init File: @file{.emacs}
@cindex init file
@@ -688,5 +688,5 @@
are swapped and the characters @kbd{C-q} and @kbd{C-^} are swapped.
After executing this function, typing @kbd{C-\} has all the usual
-effects of typing @kbd{C-s}, and vice versa. (@xref{Flow Control} for
+effects of typing @kbd{C-s}, and vice versa. (@xref{Flow Control}, for
more information on this subject.)
@@ -743,6 +743,6 @@
you will have to start Emacs afresh to make this take effect.
-@strong{Note:} In version 19, @code{baud-rate} is a variable so that you
-can change it conveniently within Emacs.
+@strong{Please note:} In version 19, @code{baud-rate} is a variable so
+that you can change it conveniently within Emacs.
@end defun
--- elisp-orig/positions.texi 1990-05-31 19:07:46.000000000 +0000
+++ elisp/positions.texi 2008-11-25 23:01:58.000000000 +0000
@@ -75,5 +75,5 @@
current buffer. This is @code{(1+ (buffer-size))}, unless narrowing is
in effect, in which case it is the position of the end of the region
-that you narrowed to. (@xref{Narrowing}).
+that you narrowed to. (@xref{Narrowing}.)
@end defun
@@ -745,5 +745,5 @@
last of @var{forms}, or @code{nil} if no forms were given.
-@strong{Note:} it is easy to make a mistake when using
+@strong{Caution:} it is easy to make a mistake when using
@code{save-restriction}. Read the entire description here before you
try it.
--- elisp-orig/processes.texi 1990-12-01 21:17:14.000000000 +0000
+++ elisp/processes.texi 2008-11-25 23:01:58.000000000 +0000
@@ -90,8 +90,8 @@
supplied to @var{program} as separate command line arguments. Wildcard
characters and other shell constructs are not allowed in these strings,
-since they are passed directly to the specified program. @strong{Note:}
-the argument @var{program} contains only the name of the program; it may
-not contain any command-line arguments. Such arguments must be provided
-via @var{args}.
+since they are passed directly to the specified program.
+@strong{Please note:} the argument @var{program} contains only the name
+of the program; it may not contain any command-line arguments. Such
+arguments must be provided via @var{args}.
The subprocess gets its current directory from the value of
--- elisp-orig/searching.texi 1990-08-29 03:21:46.000000000 +0000
+++ elisp/searching.texi 2008-11-25 23:01:58.000000000 +0000
@@ -292,10 +292,10 @@
@end table
-@strong{Note:} for historical compatibility, special characters are treated as
-ordinary ones if they are in contexts where their special meanings make no
-sense. For example, @samp{*foo} treats @samp{*} as ordinary since there is
-no preceding expression on which the @samp{*} can act. It is poor practice
-to depend on this behavior; better to quote the special character anyway,
-regardless of where it appears.@refill
+@strong{Please note:} for historical compatibility, special characters
+are treated as ordinary ones if they are in contexts where their special
+meanings make no sense. For example, @samp{*foo} treats @samp{*} as
+ordinary since there is no preceding expression on which the @samp{*}
+can act. It is poor practice to depend on this behavior; better to quote
+the special character anyway, regardless of where it appears.@refill
For the most part, @samp{\} followed by any character matches only
--- elisp-orig/strings.texi 1990-06-07 00:12:23.000000000 +0000
+++ elisp/strings.texi 2008-11-25 23:01:58.000000000 +0000
@@ -621,5 +621,5 @@
The definition of a word is any sequence of consecutive characters
that are assigned to the word constituent category in the current syntax
-table (@xref{Syntax Class Table}).
+table (@pxref{Syntax Class Table}).
When the argument to @code{capitalize} is a character, @code{capitalize}
--- elisp-orig/variables.texi 1990-12-02 18:51:32.000000000 +0000
+++ elisp/variables.texi 2008-11-25 23:01:58.000000000 +0000
@@ -425,5 +425,5 @@
of @var{symbol} to the result, provided @var{value} is given.
-@strong{Note:} don't use @code{defconst} for user option variables in
+Don't use @code{defconst} for user option variables in
libraries that are not normally loaded. The user should be able to
specify a value for such a variable in the @file{.emacs} file, so that
|