Ondřej Súkup
f3ed31b3a4
* Vim9: need more tests for empty string arguments. * Some type casts are not needed. * Cannot distinguish Normal and Terminal-Normal mode. * The ModeChanged event only uses one character for the new_mode and old_mode values. * Pattern matching with ModeChanged not tested. * nginx files are not recognized. * Cannot detect insert scroll mode. * Completion submode not indicated for virtual replace. * CursorHoldI event interferes with "CTRL-G U". (Naohiro Ono) * Problem with :cd when editing file in non-existent directory. (Yee Cheng Chin) * Some files with json syntax are not recognized. * Crash with error in :catch and also in :finally. * Crash when using CTRL-T after an empty search pattern. * Other crashes with empty search pattern not tested. * Some files with tcl syntax are not recognized. * Some places use "Vimscript" instead of "Vim script". * Expression register set by not executed put command. * Renaming a buffer on startup may cause using freed memory. * Startup test fails on MS-Windows. * Still crash with error in :catch and also in :finally. * Crash when calling job_start with an invalid argument. (Virginia Senioria) * Test does not fail without the fix for a crash. * Failures when char is unsigned. * Reading beyond end of line ending in quote and backslash. * #ifdef for using sysinfo() is incomplete. * Crash when going through spell suggestions. * Python 3 test fails with Python 3.10. OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=682
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>