- The code should be commented more - Having a shell open, cannot kill stuff by pressing ctrl-c / control chars not sent? - fine locally, not on metawire - Typing simultaneously, the cursor blinks annoyingly. - Starting a ytalk session within another one leads to scary results [so a check if ytalk already running] - automatic logging of both sides of every conversation to a new file under ~/.ytalk/, or something akin to this. - saving the current configuration to ~/.ytalkrc [does this mean a menu entry or saving of the current configuration at quit? - so /etc/ytalkrc is read the first time and then never again, as ~/.ytalkrc exists?] - saving (in memory) the full text of the current conversation and implementing scrollback with the arrow keys. - reworking the separation between the presentation and backend layers as appropriate, and writing a modern graphical interface using GTK, wxWindows or Qt. - documenting the various protocols used. - looking at the Debian bug tracker and at their packaged version of Ytalk for patches to review and bugs to fix. * Can't cut&paste in X (#16826) * Color for ytalk (#17913) [wishlist] * Re-ring keystroke (#38409) * Licensing problem (#37950) - Stuff below is from the old maintainer's BUGS file. [ the following code fails under ytalk's shell but not in other places. weird. ] See the screenshot below. As you can see, the problem is intermittent. I can't run `strace' to see what's going wrong, because ytalk breaks that too. The code in dpkg that's failing amounts to c= fork(); if (c<0) bomb_out(); if (!c) { exec(); bomb_out(); } repeatedly { rc= waitpid(c,&status); error_check(); } and it's the waitpid that's failing with ECHILD. (pending) --- RUBDEF and languages: 0xfd is used by some language encodings, but YTalk uses it to recognize itself... need to figure something out. (pending) ---