Re: After compose key cursor or function keys don't work

[Klaus Zeitler]

>>>>> "Jan" == Jan D <address@hidden> writes:
    Jan> 
    Jan> Does this patch work?
    Jan> 
    Jan> *** xterm.c.~1.867.~    2005-06-13 17:46:19.000000000 +0200
    Jan> --- xterm.c     2005-06-13 17:43:14.000000000 +0200
    Jan> ***************
    Jan> *** 6281,6286 ****
    Jan> --- 6281,6287 ----
    Jan>             if (compose_status.chars_matched > 0 && nbytes == 0)
    Jan>               break;
    Jan> 
    Jan> +           bzero (&compose_status, sizeof (compose_status));
    Jan>             orig_keysym = keysym;
    Jan> 
    Jan>           /* Common for all keysym input events.  */
    Jan> 

Yes, that looks good. Pressing a cursor or function key right after
a compose sequence works fine now. 
BTW in the middle of a compose sequence these keys are ignored, whereas e.g.
a <RET> will cause an abort of the compose sequence. Don't know if this the
expected behavior. IMHO this will do.

Thanks

Klaus


-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             address@hidden  |
 ------------------------------------------
---
When the government bureau's remedies don't match your
problem, you modify the problem, not the remedy.