629e766aa1
* Quickfix code using memory after being freed.
* Using channel timeout instead of request timeout.
* Timers don't work on Unix.
* Not checking for failed open().
* Memory leak when out of memory.
* When starting the GUI fails a swap file is left behind.
* Timer with an ":echo" command messes up display.
* Although emoji characters are ambiguous width, best is to treat
them as full width.
* Catching exception that won't be thrown.
* Having type() handle a Funcref that is or isn't a partial differently
causes problems for existing scripts.
* Comparing a function that exists on two dicts is not backwards compatible.
* string() doesn't handle a partial.
* Contents file is only for Amiga distro.
* Compiler warnings for non-virtual destructor.
* The versplit feature makes the code uneccessary complicated.
* Can't build with small features.
* Still can't build with small features.
* Still quickfix test in old style.
* Build fails with tiny features.
* Malformed channel request causes a hang.
* When a JSON message is split it isn't decoded.
* Starting job with output to buffer changes options in the current buffer.
* When 'fileformats' is set in the vimrc it applies to new buffers
but not the initial buffer.
* Emoji characters are not considered as a kind of word character.
* Channel test doesn't work with Python 2.6.
* Channel demo doesn't work with Python 2.6.
OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=337
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>