--- gforth/BUGS	2001/02/08 21:30:08	1.49
+++ gforth/BUGS	2003/02/03 08:59:28	1.52
@@ -34,3 +34,27 @@ Hendrix 3oct00 <8rdcmd$j96$1@news.IAEhv.
 
 Newline has only LF (instead of CRLF) in DOS.  Bruce Hoyt 25oct2000
 <39f7b14b$2@clear.net.nz>
+
+SIGPIPE can make Gforth hard to stop (e.g., 
+gforth -m 2M wordfreq.fs -e bye|head
+anton 30may01
+
+F. does not print trailing zeroes (e.g., "10 SET-PRECISION 125e f.")
+anton 31may01
+
+Block 0 does not work as it should: "0 block drop update save-buffers"
+does not write to the blocks file.  "0 block 1024 dump" seems to give
+the previous contents of the buffer.  Travis Bemann 10jul2001
+<3b4b4f57$0$42883$272ea4a1@news.execpc.com>
+
+When accessing a block beyond the end of the block file, the result is
+filled with spaces (this is also documented).  However, when accessing
+a previously unwritten block before the end of the block file, we will
+get a block full of zeroes on most (all?) OSs.  This inconsistency
+should be eliminated and the documentation fixed.  anton 14jul2001
+
+Path handling may have a bug:
+strace $FORTH 'fpath= .|~+/gforth s" /home/anton/threading-variations/gforth/mach32b.fs" include gforth/kernel/main.fs bye'
+tries to open gforth/kernel/gforth/kernel/aliases.fs, then
+gforth/gforth/kernel/aliases.fs, but not gforth/kernel/aliases.fs.
+anton 3 sep 2001