Re: Weirdness with Input Method/quail : how to figure out source of it?

["ISHIKAWA,chiaki" <ishikawa@yk.rim.or.jp>]

Hello,

Just to be sure that everyone understands the background of the issue:

Are you running emacs under which OS?
  Linux (which distribution)?
  FreeBSD ?
  Solaris ?

Also, is it natively run on hardware, or is it run inside
virtual environment such as
  - VirtualBox
  - VMPlayer
  - other,

on which host OS if this is the case
etc.?

I had a strange key repeat problem running linux (Debian) inside VirtualBox
running on Windows XP host a couple of years ago, and ever since I have a
a line to control key repeat in my x startup file in the linux image
in that computer.
And yes, the problem was intermittent.
But this problem was noticed on every program in the linux image, not only by Emacs,
but by shell and others. So this may not be quite the cause in your case.


Chiaki


(2013/08/16 16:31), Vladimir Lomov wrote:
> Hello,
> ** Alex Kost [2013-08-16 10:32:07 +0400]:
>
>> Vladimir Lomov <lomov.vl@gmail.com> writes:
>
>>> Does anyone know if there is a tool to automatically and interactively
>>> type text in a window (frame in Emacs terminology) with specified speed?
>>> I only tried xdotool but it 'type' very quickly (I already have idea to
>>> use xdotool and sleep to control 'type' speed).
>
>> As far as I understand, xdotool just sends KeyPress/KeyRelease with
>> XSendEvent, and sleeping is the only reasonable way to slow down (i
>> don't think there are such specific utilities).  But why do you want to
>> do it?  I didn't get whether it's correlated with your Problem 1 (some
>> kind of workaround maybe).
>
> As I emphasized in first message the Problem 1 comes occasionally: I
> could run fresh Emacs session without problem, but after some time I see
> all these weird transformations (I had to say earlier that I run Emacs
> daemon and use emacsclient to open a frame but I use such approach about
> a month, the Problem is older and shows itself even when I run simple
> 'emacs').
>
> I decided to do following: write a test script that would send to
> Emacs frame a text and see what buffer has, i.e. (is there any problems with
> it. Run this script several times (with different "type" speed) to find
> out when the Problem always shows. Further steps depends on result of
> this test.
>
> This is very tiresome so I thought there should be some way to "see"
> what happens in Emacs internals to figure out why punctuation symbols
> are so "special".
>
> ---
> WBR, Vladimir Lomov
>