37773d82fd
- Updated to revision 507, fixes the following problems
* Setting the local value of 'backupcopy' empty gives an error.
(Peter Mattern)
* Compiler warning.
* Crash when expanding a very long string.
* CTRL-W } does not open preview window. (Erik Falor)
* 'linebreak' does not work well together with Visual mode.
* Issue 26: CTRL-C does not interrupt after it was mapped and then
unmapped.
* The "precedes" entry in 'listchar' will be drawn when 'showbreak
is set and list is not.
* Cursor movement is incorrect when there is a number
column/sign/fold column and 'sbr' is displayed.
* Can't compile on a system where Xutf8SetWMProperties() is not in
the X11 library. Issue 265.
* When using ":%diffput" and the other file is empty an extra empty
line remains.
* Using byte length instead of character length for 'showbreak'.
* When 'balloonexpr' results in a list, the text has a trailing
newline. (Lcd)
* A 0x80 byte is not handled correctly in abbreviations.
* Abbreviations don't work. (Toothpik)
* Check for writing to a yank register is wrong.
* ":sign jump" may use another window even though the file is
already edited in the current window.
* test_mapping fails for some people.
* Cursor movement still wrong when 'lbr' is set and there is a
number column. (Hirohito Higashi)
* Cannot specify the buffer to use for "do" and "dp", making them
useless for three-way diff.
OBS-URL: https://build.opensuse.org/request/show/260034
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/vim?expand=0&rev=142
To select the style of XIM Input the following command line arguments,
which are handled by GTK internally, are available:
--xim-preedit [none|nothing|area|position|callbacks]
--xim-status [none|nothing|area|callbacks]
To use OnTheSpot input style, start gvim like
~$ gvim [--xim-preedit callbacks] [--xim-status callbacks]
This is also the default, which you will get without any command line arguments.
To use OverTheSpot input style, start gvim like
~$ gvim --xim-preedit position [--xim-status callbacks]
OnTheSpot input is still buggy and does not yet work right for Japanese,
therefore it is recommended to use OverTheSpot input style for Japanese.
(For Korean, OnTheSpot input style works well).
Fri Jan 26 17:57:39 2001 Mike Fabian <mfabian@suse.de>