baae1f3a23
- Updated to version 8.2.0314, fixes the following problems - refreshed vim-7.3-filetype_spec.patch * Cannot recognize a terminal in a popup window. * ModifyOtherKeys cannot be temporarily disabled. * Terminal in popup test sometimes fails. * Several lines of code are duplicated. * Some code not covered by tests. * Fileformat test fails on MS-Windows. * A few new Vim9 messages are not localized. * Fileformat test still fails on MS-Windows. * "eval" after "if 0" doesn't check for following command. * Terminal in popup test sometimes fails on Mac. * No check for a following command when calling a function fails. * Trycatch test fails. * Vim9: operator after list index does not work. (Yasuhiro Matsumoto) * Some code not covered by tests. * The "num64" feature is available everywhere and building without it causes problems. * ":helptags ALL" gives error for directories without write permission. (Matěj Cepl) * Hang with combination of feedkeys(), Ex mode and :global. (Yegappan Lakshmanan) * Some Ex code not covered by tests. * Vim9: not allowing space before ")" in function call is too restrictive. (Ben Jackson) * Vim9: not all instructions covered by tests. * Channel test is flaky on Mac. * Vim9: no test for deleted :def function. * Vim9: throw in :def function not caught higher up. * Two placed signs in the same line are not combined. E.g. in the terminal OBS-URL: https://build.opensuse.org/request/show/779065 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/vim?expand=0&rev=252
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>