aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Kangas2021-04-02 19:32:32 +0200
committerStefan Kangas2021-04-03 00:53:43 +0200
commit74a86c1acf951da7451c3c8a1cd6ec277f782d41 (patch)
treeb44f7cd2102ca191e0980dba434a6dc2c210295c
parentb65a1cfed7371e27130db9e9a05f8e656ee77c6f (diff)
downloademacs-74a86c1acf951da7451c3c8a1cd6ec277f782d41.tar.gz
emacs-74a86c1acf951da7451c3c8a1cd6ec277f782d41.zip
Remove references to very old versions of Emacs from eintr
* doc/lispintro/emacs-lisp-intro.texi (Making Errors) (Void Function, Void Variable, Wrong Type of Argument, debug) (debug-on-entry): Remove commented out references to Emacs 20 or earlier. * doc/lispintro/emacs-lisp-intro.texi (what-line) (print-elements-of-list, debug, X Axis Tic Marks): Don't call version 22 or earlier a "recent" version of Emacs.
-rw-r--r--doc/lispintro/emacs-lisp-intro.texi96
1 files changed, 12 insertions, 84 deletions
diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index 5b15a456ff0..fade4096e38 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -1364,19 +1364,6 @@ C-e}:
1364(this is an unquoted list) 1364(this is an unquoted list)
1365@end smallexample 1365@end smallexample
1366 1366
1367@ignore
1368@noindent
1369What you see depends on which version of Emacs you are running. GNU
1370Emacs version 22 provides more information than version 20 and before.
1371First, the more recent result of generating an error; then the
1372earlier, version 20 result.
1373
1374@need 1250
1375@noindent
1376In GNU Emacs version 22, a @file{*Backtrace*} window will open up and
1377you will see the following in it:
1378@end ignore
1379
1380A @file{*Backtrace*} window will open up and you should see the 1367A @file{*Backtrace*} window will open up and you should see the
1381following in it: 1368following in it:
1382 1369
@@ -1838,19 +1825,6 @@ Debugger entered--Lisp error: (void-function fill-column)
1838(Remember, to quit the debugger and make the debugger window go away, 1825(Remember, to quit the debugger and make the debugger window go away,
1839type @kbd{q} in the @file{*Backtrace*} buffer.) 1826type @kbd{q} in the @file{*Backtrace*} buffer.)
1840 1827
1841@ignore
1842@need 800
1843In GNU Emacs 20 and before, you will produce an error message that says:
1844
1845@smallexample
1846Symbol's function definition is void:@: fill-column
1847@end smallexample
1848
1849@noindent
1850(The message will go away as soon as you move the cursor or type
1851another key.)
1852@end ignore
1853
1854@node Void Variable 1828@node Void Variable
1855@subsection Error Message for a Symbol Without a Value 1829@subsection Error Message for a Symbol Without a Value
1856@cindex Symbol without value error 1830@cindex Symbol without value error
@@ -1907,18 +1881,6 @@ Since @code{+} does not have a value bound to it, just the function
1907definition, the error message reported that the symbol's value as a 1881definition, the error message reported that the symbol's value as a
1908variable was void. 1882variable was void.
1909 1883
1910@ignore
1911@need 800
1912In GNU Emacs version 20 and before, your error message will say:
1913
1914@example
1915Symbol's value as variable is void:@: +
1916@end example
1917
1918@noindent
1919The meaning is the same as in GNU Emacs 22.
1920@end ignore
1921
1922@node Arguments 1884@node Arguments
1923@section Arguments 1885@section Arguments
1924@cindex Arguments 1886@cindex Arguments
@@ -2197,19 +2159,6 @@ addition had been passed the correct type of object, the value passed
2197would have been a number, such as 37, rather than a symbol like 2159would have been a number, such as 37, rather than a symbol like
2198@code{hello}. But then you would not have got the error message. 2160@code{hello}. But then you would not have got the error message.
2199 2161
2200@ignore
2201@need 1250
2202In GNU Emacs version 20 and before, the echo area displays an error
2203message that says:
2204
2205@smallexample
2206Wrong type argument:@: number-or-marker-p, hello
2207@end smallexample
2208
2209This says, in different words, the same as the top line of the
2210@file{*Backtrace*} buffer.
2211@end ignore
2212
2213@node message 2162@node message
2214@subsection The @code{message} Function 2163@subsection The @code{message} Function
2215@findex message 2164@findex message
@@ -6663,9 +6612,9 @@ original text of the function:
6663@end group 6612@end group
6664@end smallexample 6613@end smallexample
6665 6614
6666(In recent versions of GNU Emacs, the @code{what-line} function has 6615(In modern versions of GNU Emacs, the @code{what-line} function has
6667been expanded to tell you your line number in a narrowed buffer as 6616been expanded to tell you your line number in a narrowed buffer as
6668well as your line number in a widened buffer. The recent version is 6617well as your line number in a widened buffer. The modern version is
6669more complex than the version shown here. If you feel adventurous, 6618more complex than the version shown here. If you feel adventurous,
6670you might want to look at it after figuring out how this version 6619you might want to look at it after figuring out how this version
6671works. You will probably need to use @kbd{C-h f} 6620works. You will probably need to use @kbd{C-h f}
@@ -10392,9 +10341,8 @@ echo area: @code{^Jgazelle^J^Jgiraffe^J^Jlion^J^Jtiger^Jnil}, in which
10392each @samp{^J} stands for a newline.) 10341each @samp{^J} stands for a newline.)
10393 10342
10394@need 1500 10343@need 1500
10395In a recent instance of GNU Emacs, you can evaluate these expressions 10344You can evaluate these expressions directly in the Info buffer, and
10396directly in the Info buffer, and the echo area will grow to show the 10345the echo area will grow to show the results.
10397results.
10398 10346
10399@smallexample 10347@smallexample
10400@group 10348@group
@@ -18104,8 +18052,7 @@ argument of 4:
18104@end smallexample 18052@end smallexample
18105 18053
18106@noindent 18054@noindent
18107In a recent GNU Emacs, you will create and enter a @file{*Backtrace*} 18055This will create and enter a @file{*Backtrace*} buffer that says:
18108buffer that says:
18109 18056
18110@noindent 18057@noindent
18111@smallexample 18058@smallexample
@@ -18139,25 +18086,12 @@ In practice, for a bug as simple as this, the Lisp error line will
18139tell you what you need to know to correct the definition. The 18086tell you what you need to know to correct the definition. The
18140function @code{1=} is void. 18087function @code{1=} is void.
18141 18088
18142@ignore
18143@need 800
18144In GNU Emacs 20 and before, you will see:
18145
18146@smallexample
18147Symbol's function definition is void:@: 1=
18148@end smallexample
18149
18150@noindent
18151which has the same meaning as the @file{*Backtrace*} buffer line in
18152version 21.
18153@end ignore
18154
18155However, suppose you are not quite certain what is going on? 18089However, suppose you are not quite certain what is going on?
18156You can read the complete backtrace. 18090You can read the complete backtrace.
18157 18091
18158In this case, you need to run a recent GNU Emacs, which automatically 18092Emacs automatically starts the debugger that puts you in the
18159starts the debugger that puts you in the @file{*Backtrace*} buffer; or 18093@file{*Backtrace*} buffer. You can also start the debugger manually
18160else, you need to start the debugger manually as described below. 18094as described below.
18161 18095
18162Read the @file{*Backtrace*} buffer from the bottom up; it tells you 18096Read the @file{*Backtrace*} buffer from the bottom up; it tells you
18163what Emacs did that led to the error. Emacs made an interactive call 18097what Emacs did that led to the error. Emacs made an interactive call
@@ -18197,14 +18131,8 @@ then run your test again.
18197@section @code{debug-on-entry} 18131@section @code{debug-on-entry}
18198@findex debug-on-entry 18132@findex debug-on-entry
18199 18133
18200A recent GNU Emacs starts the debugger automatically when your 18134Emacs starts the debugger automatically when your function has an
18201function has an error. 18135error.
18202
18203@ignore
18204GNU Emacs version 20 and before did not; it simply
18205presented you with an error message. You had to start the debugger
18206manually.
18207@end ignore
18208 18136
18209Incidentally, you can start the debugger manually for all versions of 18137Incidentally, you can start the debugger manually for all versions of
18210Emacs; the advantage is that the debugger runs even if you do not have 18138Emacs; the advantage is that the debugger runs even if you do not have
@@ -20079,8 +20007,8 @@ the tic marks themselves and their spacing:
20079@code{defvar}. The @code{boundp} predicate checks whether it has 20007@code{defvar}. The @code{boundp} predicate checks whether it has
20080already been set; @code{boundp} returns @code{nil} if it has not. If 20008already been set; @code{boundp} returns @code{nil} if it has not. If
20081@code{graph-blank} were unbound and we did not use this conditional 20009@code{graph-blank} were unbound and we did not use this conditional
20082construction, in a recent GNU Emacs, we would enter the debugger and 20010construction, we would enter the debugger and see an error message
20083see an error message saying @samp{@w{Debugger entered--Lisp error:} 20011saying @samp{@w{Debugger entered--Lisp error:}
20084@w{(void-variable graph-blank)}}.) 20012@w{(void-variable graph-blank)}}.)
20085 20013
20086@need 1200 20014@need 1200