fb30f470bc
- Updated to revision 627, fixes the following problems * Call for requesting color and ambiwidth is too early. (Hirohito Higashi) * "1gd" may hang. * Bracketed paste is still enabled when executing a shell command. (Michael Smith) * Can't run make with several jobs, creating directories has a race condition. * The cursor line number becomes negative when using :z^ in an empty buffer. (neovim #6557) * Building the command table requires Perl. * Running parallel make after distclean fails. (Manuel Ortega) * Get only one quickfix list after :caddbuf. * Using freed memory when resetting 'indentexpr' while evaluating it. (Dominique Pelle) * Can't build when configure choses "install-sh". (Daniel Hahler) * Warning for uninitialized variable. (John Marriott) * :simalt on MS-Windows does not work properly. * Duplicate test case for quickfix. * Cannot set the valid flag with setqflist(). * Moving folded text is sometimes not correct. * Illegal memory access with z= command. (Dominique Pelle) * Fold test hangs on MS-Windows. * Memory leak when executing quickfix tests. * Test_options fails when run in the GUI. * No test for mapping timing out. * Configure check for return value of tgetent is skipped. * job_stop() often assumes the channel will be closed, while the job may not actually be stopped. (Martin Gammelsæter) * :simalt still does not work. * Cannot add a context to locations. OBS-URL: https://build.opensuse.org/request/show/501354 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/vim?expand=0&rev=192
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>