23.0.50: erc and quail problem

23.0.50: erc and quail problem

[John J Foerch]

Hello,

I'm able to reproduce a problem with the following steps in both gui
and non-gui invocations of emacs 23 from CVS, on a Debian Lenny
machine.

  Run: emacs -Q
  M-x erc RET
  ; connect to irc with defaults at all prompts
  ; change buffer to *scratch*
  C-\ chinese-py RET
  n e <backspace> <backspace>
  ; now wait at least a minute, then type a character; it does
  ; not go to the input method.  instead, it appears in the buffer
  ; as ordinary ascii.

I don't believe the problem has to do with the `chinese-py' input
method itself, because I also reproduced it with another input method
that is not part of emacs, `chinese-wubi'.

Hope this helps,
Thanks,
John Foerch

processes, read-char, and quail problem

[John J Foerch]

Hello,

Bojohan investigated a bug I originally reported as a quail+erc bug.
He found that the problem is not particular to erc, but can be
reproduced with any process, and that the bug seems to be in emacs
`read_char'.  I will quote what he told me.  The conversation was on
irc so I have changed the formatting.

### quote

To reproduce, try:

 * emacs -Q
 * M-x server-start RET
 * C-\ chinese-py RET
 * x <backspace>
 * emacsclient --eval 0
 * x

`read_char' contains this condition:

   /* Pass this to the input method, if appropriate.  */
   if (INTEGERP (c)
       && ! NILP (Vinput_method_function)
       /* Don't run the input method within a key sequence,
 	 after the first event of the key sequence.  */
       && NILP (prev_event)
       [...]

The input method does it's own event reading in a loop. accepting
process input interrupts it. `read_key_sequence' reenters `read_char',
but this time prev_event isn't nil.  It's `backspace'.

Processing input calls `record_asynch_buffer_change':

   /* Put a BUFFER_SWITCH_EVENT in the buffer so that read_key_sequence
     will notice the new current buffer. */

When `read_key_sequence' continues reading chars it is in the middle
of a sequence and the input method is skipped.  So basically, normally
"x <backspace> x ..." happens within the one and same invocation of
read_char. when a process intervenes, read_key_sequence resumes in the
middle of the sequence.

### end quote

I hope this information can be of use.

Thank you,
John Foerch