--- gforth/BUGS	1994/05/07 14:55:44	1.2
+++ gforth/BUGS	1996/08/26 10:07:17	1.22
@@ -1,23 +1,17 @@
-The system quits on exceptions like segmentation faults. anton 5oct93
-
-compile does not have its traditional meaning. anton 5oct93
-
-include does not read the last line if it does not end with \n.  anton 6oct93
-
-in decimal mode aaa is accepted as 1110  anton 4feb94
-
-abort" does something to the control flow stack  anton 2mar94
-
-the compiler does not complain about undefined words; instead, it
-complains about unstructured  anton 2mar94
-
-the compiler tries to reveal anonymous words ( -> redefined complaints )  anton 2mar94
-
-'ansforth "include xxx"' gives a segmentation fault after processing
-the file; No segmentation fault when including from the Forth prompt
-anton 2apr94
-
-name> does not take the same argument as e.g. .name. Remedy: add cell+
-before name>, but adapt all uses.  anton 23apr94
+etags.fs crashes one of my applications (gs.fs). anton 12jan95
 
+gforth.el: indentation does not work right on the first line of a
+buffer. anton 27jan95
 
+Conditional compilation continues after the file ends. This is allowed
+by the standard (through an ambiguous condition), but the compiler
+should at least produce a warning.  anton 27jan95
+
+DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py
+
+see does not leave a space after two-digit literals:
+  : xxx 50 ;
+  see xxx
+gives
+  : xxx  
+  50;