1-*-indented-text-*-
2
3From the authors of cancan:
4
5    THINGS TO DO
6	  Cancan should know the codes of at least some keys
7	  by looking in the TERMCAP. (especially control keys are trivial!)
8
9	- Run (a)lint!
10
11	- There seems to be problems with running cancan on exotic terminals.
12	  This defeats the very purpose of all the carefully terminal-
13	  independent code with TERMCAP, and is generally embarrassing.
14
15	- more system calls should be checked for EINTR for sysV unices
16
17	- negotiate the telnet BINARY option
18
19	- support the telnet IAC GA command to identify prompts
20	  (But what for? Prompts have to be identified as such in the absence
21	   of GA anyway, and there doesn't seem to be a need for it right
22	   now.)
23
24	- implement reverse-incremental-search (like ^R in GNU Readline)
25
26    KNOWN BUGS
27	- Deleting more than one character with deletechar() might leave
28	  ugly traces on lines that are entirely deleted.
29
30	- using #hilite with coloured background might have effects beyond the
31	  input line, depending on the terminal (don't do that, then :-)
32
33    FUTURE POSSIBLE IMPROVEMENTS
34	Do some more for portability (clean up the terminal mess)
35	The source should be more modular
36	Filtering output through shell command (grep etc)
37
38
39THINGS TO DO/PLANNED IMPROVEMENTS on powwow:
40       - make a better #help
41       - add termcap "end of bold", "end of blink" etc.
42
43       If you have ideas, suggestions or whatever, e-mail them to me
44       (max@Linuz.sns.it) and if I find them interesting, I will add them.
45       Also, I am trying to keep powwow updated with further releases
46       of cancan.
47