1 
 2 09/21/87  qedx
 3 Known errors in the current release of qedx.
 4 #         Associated TR's
 5 Description
 6 
 7 0016  phx17590 phx18344
 8  If the user types an input/request line longer than 512 characters,
 9  qedx will overwrite parts of the stack causing subsequent faults or
10  fatal process errors.
11 
12 0011  phx16226
13  The "wake_tbl" tty_ mode, which causes the user's process to only
14  be awoken when a "\" is typed, is not reset if the current buffer
15  overflows (ie:  exceeds 1044480 characters) during input.
16 
17 0010  phx15534 phx15664
18  qedx should not create files whose names require the use of quoting
19  or special control arguments (eg: rename's "-name") as the
20  manipulation of such files pose severe problems for naive (and not
21  so naive) users.  Thus, qedx should reject the use of whitespace,
22  command language characters ("()[];), starname characters (*?),
23  and equalname characters (=%) when creating a new file.
24 
25 0009  phx15606
26  qedx ignores empty buffers when deciding whether to ask for permis-
27  sion to exit with modified buffers.  However, the list of
28  modified buffers displayed in the query includes empty buffers.
29  Empty buffers should not be listed.  This is a bug because a user
30  will not be able to reset the modified state of these buffers as
31  qedx does not allow the user to write an empty buffer but the
32  empty buffers will continue to be listed as long as there is one
33  non-empty, modified buffer.
34 
35 0008  phx15457 phx19279
36  Given the following sequence of qedx requests:
37       r FILE
38       b(other) $a \b(0) \f
39  the text appended to buffer "other" will not contain the contents
40  of the file that was just read into buffer "0".
41 
42 0007  phx15204 phx18060
43  Given the following sequence of requests in an empty buffer:
44       .r FILE
45       1p 1,$d
46       .r FILE
47       1p 1,$d
48       .r FILE
49       1p
50  the first read request will execute properly.  However, the second
51  read request will insert a NUL at the beginning of the file as
52  seen by the print request.  The third and subsequent read requests
53  will insert a newline at the beginning of the file.