--- gforth/Attic/gforth.ds	1995/11/30 18:04:27	1.26
+++ gforth/Attic/gforth.ds	1996/01/07 17:22:09	1.29
@@ -91,7 +91,7 @@ personal machines. This manual correspon
 * Emacs and Gforth::            The Gforth Mode
 * Internals::                   Implementation details
 * Bugs::                        How to report them
-* Pedigree::                    Ancestors of Gforth
+* Origin::                      Authors and ancestors of Gforth
 * Word Index::                  An item for each Forth word
 * Node Index::                  An item for each node
 @end menu
@@ -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:
@@ -3718,7 +3726,7 @@ used here. The paper available at
 it also contains numbers for some native code systems. You can find
 numbers for Gforth on various machines in @file{Benchres}.
 
-@node Bugs, Pedigree, Internals, Top
+@node Bugs, Origin, Internals, Top
 @chapter Bugs
 
 Known bugs are described in the file BUGS in the Gforth distribution.
@@ -3738,8 +3746,20 @@ For a thorough guide on reporting bugs r
 to Report Bugs, gcc.info, GNU C Manual}.
 
 
-@node Pedigree, Word Index, Bugs, Top
-@chapter Pedigree
+@node Origin, Word Index, Bugs, Top
+@chapter Authors and Ancestors of Gforth
+
+@section Authors and Contributors
+
+The Gforth project was started in mid-1992 by Bernd Paysan and Anton
+Ertl. The third major author was Jens Wilke. Lennart Benschop (who also
+was one of Gforth's first users, in mid-1993) and Stuart Ramsden
+inspired us with their continuous feedback. Lennart Benshop contributed
+@file{glosgen.fs}, while Stuart Ramsden has been working on automatic
+support for calling C libraries. Helpful comments also came from Paul
+Kleinrubatscher, Christian Pirker, Dirk Zoller and Marcel Hendrix.
+
+@section Pedigree
 
 Gforth descends from BigForth (1993) and fig-Forth. Gforth and PFE (by
 Dirk Zoller) will cross-fertilize each other. Of course, a significant
@@ -3774,7 +3794,7 @@ H. Moore, presented at the HOPL-II confe
 Notices 28(3), 1993.  You can find more historical and genealogical
 information about Forth there.
 
-@node Word Index, Node Index, Pedigree, Top
+@node Word Index, Node Index, Origin, Top
 @chapter Word Index
 
 This index is as incomplete as the manual. Each word is listed with