5fde9a46e1
* Packadd test does not clean up symlink.
* Packadd test uses wrong directory name.
* The E11 error message in the command line window is not translated.
* The "zero count" error doesn't have a number. (Hirohito Higashi)
* Xfontset and guifontwide are not tested.
* Illegal memory access after "vapo". (Dominique Pelle)
* Restoring help snapshot accesses freed memory. (Dominique Pelle)
* GUI test fails on some systems.
* Illegal memory access when 'complete' ends in a backslash.
* Can't access b:changedtick from a dict reference.
* Functions test fails.
* Flags of :substitute not sufficiently tested.
* Invalid memory access in :recover command.
* :recover test fails on MS-Windows.
* Illegal memory access with vi'
* Not checking return valud of dict_add(). (Coverity)
* When using complete() and typing a character undo is saved after the
character was inserted. (Shougo)
* Double free when compiled with EXITFREE and setting 'ttytype'.
* b:changedtick can be unlocked, even though it has no effect.
* Unlet command leaks memory. (Nikolai Pavlov)
* islocked('d.changedtick') does not work.
* Vim relies on limits.h to be included indirectly, but on Solaris 9 it
may not be. (Ben Fritz)
* When using CTRL-X CTRL-U inside a comment, the use of the comment leader
may not work. (Klement)
* When building with a shadow directory on macOS lacks the +clipboard
feature.
* Redrawing errors with GTK 3.
OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=421
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>