cb34494a93
* Cannot detect a crash in tests when caused by garbagecollect().
* The help for functions require a space after the "(".
* The Perl interface cannot use 'print' operator for writing
directly in standard IO.
* It is not easy to get a character out of a string.
* Python: turns partial into simple funcref.
* Folds may close when using autocomplete.
* Test fails when not using utf-8.
* It is not possible to only see part of the message history.
It is not possible to clear messages.
* Count for ":messages" depends on number of lines.
* syn-cchar defined with matchadd() does not appear if there are no
other syntax definitions which matches buffer text.
* Not testing utf-8 characters.
* strgetchar() does not work correctly.
* Clang warns for uninitialzed variable. (Michael Jarvis)
* Python: Converting a sequence may leak memory.
* Memory leak in Perl.
* Coverity: missing check for NULL pointer.
* "gD" does not find match in first column of first line.
* When using GTK 3.20 there are a few warnings.
OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=349
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>