Ondřej Súkup
860d57a7f5
* Crash when using search stat in narrow screen. * Using sizeof() and subtract array size is tricky. * Typo in pattern for filetype detection. * "1v" may select block with wrong size. (Evgeni Chasnovski) * FIRRTL files are not recognized. * The code for setting options is too complicated. * Some mappings with Meta and Shift do not work. * Cursor may move with autocmd in Visual mode. * go.work.sum files are not recognized. * Display shows lines scrolled down erroneously. (Yishai Lerner) * Inssufficient testing for what 9.0.1265 fixes. * Cadence files are not recognized. * Ron files are not recognized. * The code for setting options is too complicated. * Compiler warnings for uninitialized variables. (Tony Mechelynck) * Various small problems. * Coverity warns for using a NULL pointer. * With the Kitty key protocl Esc with NumLock cannot be mapped. * FunC files are not recognized. * A newer version of clang can be used for CI. * CTRL-N and -P on cmdline don't trigger CmdlineChanged. * Move language files are not recognized. * :defer may call the wrong method for an object. (Ernie Rael) * The set_num_option() is too long. * The set_bool_option() function is too long. * The option initialization function is too long. * Calling an object method with arguments does not work. (Ernie Rael) * Wrong value for $LC_CTYPE makes the environ test fail. * Inserting a register on the command line does not trigger incsearch or OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=782
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>