Re: Isearch and postfix input methods.

[Kenichi Handa]

In article <address@hidden>, Juri Linkov <address@hidden> writes:

>>  When you type "o", isearch searches for "o" even if "o" is
>>  not yet fixed.  Then when you type, for instance, "'", "ó"
>>  is searched for from the first search position, and move
>>  point to the found position regardless of that position
>>  being before or after the previously found "o".  So, isearch
>>  sometimes moves point back and forward.

>>  But, for the moment, no one has worked on implementing it.

> This looks like the most natural way of searching with active
> input methods.  Though, I don't see how this can be implemented,
> if read-string in isearch-process-search-multibyte-characters
> can't quit until the input sequence is finished.

One idea is to make input method function accept
INPUT-CONTEXT as the second arg, update it, and return
(EVENT-SEQ . INPUT-CONTEXT) instantly.  In the case of "o",
the returned EVENT-SEQ is nil which means no events to
propagate but INPUT-CONTEXT can carry information about the
current preedit string (i.e. "o") as well as the other
information used for handling the next key.

---
Kenichi Handa
address@hidden