cddb525664
- Switch back to GTK+2 because GTK+3 interface seems to be slower. - Updated to revision 1525, fixes the following problems * Statusline highlighting is sometimes wrong. * "J" fails if there are not enough lines. * Channel output to file not implemented yet. * Channel test is a bit flaky. * Channel with disconnected in/out/err is not supported. * Channel test: Waiting for a file to appear doesn't work. * Cannot write channel err to a buffer. * On a high resolution screen the toolbar icons are too small. - Updated to revision 1510, fixes the following problems * Crash when starting a job fails. * Keeping both a variable for a job and the channel it refers to is a hassle. * Channel test fails on AppVeyor. - Updated to revision 1506, fixes the following problems * No error message when :packadd does not find anything. * Garbage collection with an open channel is not tested. * Writing last-but-one line of buffer to a channel isn't implemented yet. * Crash when using ch_getjob(). * No test for reading last-but-one line. * When channel log is enabled get too many "looking for messages" log entries. * Job cannot read from a file. - Updated to revision 1498, fixes the following problems * ":loadplugin" is not optimal, some people find it confusing. * Not using key when result from hangul_string_convert() is NULL. * "inline" is not supported by old MSVC. OBS-URL: https://build.opensuse.org/request/show/369495 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/vim?expand=0&rev=169
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>