1 
 2 09/21/87  dial_out
 3 Known errors in the current release of dial_out.
 4 #         Associated TR's
 5 Description
 6 
 7 23  phx20495
 8 dial_out -raw translates LFs typed by the user into CRs transmitted
 9 down the comm line.  It's difficult to transmit a raw LF.
10 
11 22  phx18903
12 "quit" mode should imply tty_ "^hndlquit" mode.
13 
14 21  phx18645
15 dial_out raw mode doesn't work in the Video System.
16 
17 19  phx18127
18 A recursive invocation of "dial_out -profile X" will terminate
19 X.profile too many times, causing the outer invocation to fault.  This
20 error also affects non-recursive uses of dial_out when the profile
21 being used is also being used by another application (e.g.  the default
22 command processor profile if the dial_out user just specifies -abbrev
23 and lets the profile default).
24 
25 18  phx17769
26 The terminal type specified with dial_out -ttp should be uppercased
27 before the set_term_type control order is issued.
28 
29 16  phx15559
30 If using "quit" mode, then any error returned while sending the
31 interrupt because of hitting BREAK causes dial_out to abort the entire
32 invocation.
33 
34 15  phx16761 phx19733 phx20154
35 If there is a syntax error in the "-modes" parameter, random errors,
36 and sometimes fatal process errors, can occur.  This is because the
37 cleanup handler restores the cl_intermediary, even though the variable
38 used to save the cl_intermediary has not been set.
39 
40 8  phx16403
41 If you suspend dial_out, change your tty modes, and then start up the
42 dial_out, when you later exit dial_out your modes will be back the way
43 they were when you started dial_out initially.
44 
45 7  phx16150
46 The send_file request faults if the pathname argument is not given.
47 
48 5  phx16304
49 The wait request doesn't always clean up its timer.
50 
51 3  phx16306
52 The "quit" and "interrupt" requests do not complain if given arguments,
53 although they ignore them.