Andrei A. Voropaev wrote:

> On Wed, May 10, 2006 at 05:08:43PM +0200, Bram Moolenaar wrote:
> > 
> > To be able to look into this I need an exact desciption of what you are
> > doing.  Start with "vim -u NONE" to avoid any of your startup scripts.
> > Since it depends on the text you enter, you need to mention that too.
> > 
> 
> In the simplest case I start vim the following shell script.
> 
>    #!/bin/bash

It already fails here, I don't have /bin/bash.  I tried doing it with
"env" but the value for XMODIFIERS includes an '=' and that's not valid.
I don't have a "scim" program.

>    export GTK_IM_MODULE=scim XIM_PROGRAM="scim -d" [EMAIL PROTECTED] 
> LC_CTYPE=en_US.UTF-8
>    exec vim -g -U NONE -U ~/.gjprc "$@"
> 
> the content of .gjprc
> 
>    set guifont=Fixed\ 12
>    colorscheme darkblue
>    set guioptions-=T
>    set keymap=russian-jcuken
> 
> I start with empty file.
>
> Then add any text in russian or in english. Make modifications to it. Do
> undo/redo. Everything works. Now I insert any text in Japanese. Leave
> insert mode. After that add more text, leave insert mode, add more text,
> leave insert mode (repeat couple times). Now hit "u". Everything
> starting with japanese text disappears. The changes done before entering
> Japanese text stay in tact. Hitting Ctrl-r restores everything.
> 
> Now I add more Japanese text at the end of the document. Again
> english/russian after it. Hitting "u" removes everything to the moment
> when first japanese was entered. Hit Ctrl-r to restore it.
>
> Now, go in the middle of the text (between 2 of the japanese sentences)
> and enter some japanese there. Now again add some text anywhere. Hit "u"
> after that. I get the error E438 and after that any attempts to hit "u"
> produce unexpected results :)
> 
> The text itself does not make any difference :)

Well, you say it must be japanese, thus it does matter.  I have no idea
how to enter russian or japanese.  I'll have to leave this to someone
else.

Does the problem go away if you don't use the input method?  Then that's
probably the cause of the problem.

-- 
The primary purpose of the DATA statement is to give names to constants;
instead of referring to pi as 3.141592653589793 at every appearance, the
variable PI can be given that value with a DATA statement and used instead
of the longer form of the constant.  This also simplifies modifying the
program, should the value of pi change.
        -- FORTRAN manual for Xerox Computers

 /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Reply via email to