David Monniaux wrote:
> While this seems to act up haphazardly, there seems to be a way to reliably reproduce the error:
> * activate SCIM for your locale (using im-switch) and restart the session (there is no need to actually run a SCIM input method; it suffices that SCIM is active)
> * start Eclipse
> * start typing away a small Java program including: System.out.println("something")
This is a known problem with java. Does this also happen with other
non-java applications?
Maybe related to the fact that java uses the XIM protocol, which is not
very reliable. BUt I'm not sure if the bug is in scim or in java.
David Monniaux wrote: out.println( "something" )
> While this seems to act up haphazardly, there seems to be a way to reliably reproduce the error:
> * activate SCIM for your locale (using im-switch) and restart the session (there is no need to actually run a SCIM input method; it suffices that SCIM is active)
> * start Eclipse
> * start typing away a small Java program including: System.
This is a known problem with java. Does this also happen with other
non-java applications?
Maybe related to the fact that java uses the XIM protocol, which is not
very reliable. BUt I'm not sure if the bug is in scim or in java.