--- gforth/Attic/gforth.ds	1995/11/30 18:04:27	1.26
+++ gforth/Attic/gforth.ds	1995/12/23 16:21:57	1.28
@@ -2528,9 +2528,14 @@ The next invocation of a parsing word re
 Compiles a recursive call to the defining word not to the defined word.
 
 @item argument input source different than current input source for @code{RESTORE-INPUT}:
-If the argument input source is a valid input source then it gets
-restored. Otherwise the result is undefined.
-@comment causes @code{-12 THROW}, which, unless caught, issues the message "argument type mismatch" and aborts. !! not all of the state is restored (e.g., sourcefilename).
+@code{-12 THROW}. Note that, once an input file is closed (e.g., because
+the end of the file was reached), its source-id may be
+reused. Therefore, restoring an input source specification referencing a
+closed file may lead to unpredictable results instead of a @code{-12
+THROW}.
+
+In the future, Gforth may be able to retore input source specifications
+from other than the current input soruce.
 
 @item data space containing definitions gets de-allocated:
 Deallocation with @code{allot} is not checked. This typically resuls in
@@ -3238,7 +3243,10 @@ Also, if you @code{include} @file{etags.
 contains the definitions of all words defined afterwards. You can then
 find the source for a word using @kbd{M-.}. Note that emacs can use
 several tags files at the same time (e.g., one for the Gforth sources
-and one for your program).
+and one for your program, @pxref{Select Tags Table,,Selecting a Tags
+Table,emacs, Emacs Manual}). The TAGS file for the preloaded words is
+@file{$(datadir)/gforth/$(VERSION)/TAGS} (e.g.,
+@file{/usr/local/share/gforth/0.2/TAGS}).
 
 To get all these benefits, add the following lines to your @file{.emacs}
 file: