> Perhaps this is where the problem lies. I haven't done anything for ncurses to > handle multibyte input (which is what I understand dead-keys to be). If > ncurses sees that as 3 characters, it'll think that's how long it displays via > a prompt. So the repainting would be farther to the right, etc. (My > understanding of dead-keys or compose was that the byte stream is processed in > the input-method or the keyboard handler, before the terminal emulator sees > that).
No, dead keys enable me to hit apostrope ' and then e to get é. It used to be called "Compose" on some systems and keyboards that had a compose button. ISO-8859-1 is just a specific rule for understanding extended ASCII characters, and not double-byte. Double byte languages are ones that do not use regular latin characters, like sengalese, arabic, hebrew... > The text I sent could be copied to a file and compiled with 'tic', so that > setting $TERM to 'konsole' would pick up that entry. There's probably an > older 'konsole' entry already there, but I reviewed that, and gnome-terminal > in the past few months to update them. I'm not sure this will help; I don't want to screw things up. Everything else I have run with curses has behaved OK. Mutt even seems to run beautifully apart from this issue. To expand further, can anyone else reproduce this? Hit "s" on an email from someone with more than 8 characters before the @ then hit backspace a few times. As you approach the 8th character (or perhaps the 7th if Mutt has added an =) when you hit backspace, the cursor actually jumps forward after the delete. This appears to be the start of the problem. -- |-Simon White |-Internet Services Manager |-MTDS S.A. |-tel +212.3.767.4861 |-fax +212.3.767.4863 |-14, rue 16 novembre |-Rabat, Kingdom of Morocco
