--- gforth/BUGS	1994/08/19 17:47:18	1.6
+++ gforth/BUGS	1995/10/07 17:42:14	1.20
@@ -1,22 +1,19 @@
-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
 
-revealing the same name several times (e.g., by using recursive)
-results in redefined messages.  anton 28jul94
+not all aliases are in the etags file. Bug in etags.fs? anton 24jan95
+-> wrote special tag generation for cross compilation. bernd 6sep95
 
-[IF] is case-sensitive.  anton 2aug94
+emacs often finds the wrong tag. anton 24jan95
+-> emacs does not search for a complete word, but for parts.
+-> Solution: add blanks in front and end of tag name (etags.fs)
+-> and use own forth-find-tag. bernd 6sep95
 
-if blocks.fb does not exist, 1 block creates the file, but cannot
-read-file from it. Only if the file-id has been created with
-open-file, not create-file, read-file works. - anton 6aug94
+gforth.el: indentation does not work right on the first line of a
+buffer. anton 27jan95
+-> Solved?
 
-gforth.el: doing a forth-fill-paragraph on the following piece of code
-uncomments the first comment line. This may be a bug in
-fill-paragraph, but documentation says that a paragraph can start
-without prefix (hanging indentation), so I guess it's all right. -
-anton 19aug94
+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
 
-: bb-shortest-paths recursive { bb bb-from start-path -- }
-    \ compute the
-    \ paths from bb-from through bb, start-path is the path from
-    \ bb-from to bb
+DOS and OS/2 don't like . at begin of a file (.gforth-history). bernd 6sep95py
\ No newline at end of file