Ondřej Súkup
40514c8344
* The first termcap entry of a builtin termcap is not used. * Two conditions are always false. * Coverity warns for not using return value of dict_add(). * Coverity warns for using a NULL pointer. * Using Ruby LDFLAGS may cause build problems. * Build failure with tiny version. (Tony Mechelynck) * Cannot debug the Kitty keyboard protocol with TermDebug. * Oblivion files are not recognized. * Kitty shows "already at oldest change" on startup. * Various code formatting issues. * When using dash it may not be recognize as filetype "sh". * Wrong type for "isunnamed" returned by getreginfo(). * Forked repositories send out useless email. * Still using simplified mappings when using the kitty keyboard protocol. * Crash when typing a letter in a terminal window. (Shane-XB-Qian) * CI failures in sound dummy. * Workflow Description Language files are not recognized. * Pretending to go out of Insert mode when Esc is received has side effects. * 'cursorline' causes virtual text highlight to continue. * Failures in the cursorline test. * CI: Error in Coverity flow is not reported. * Invalid memory access in substitute with function that goes to another file. * 'ttyfast' is set for arbitrary terminals. * Crash when unletting a variable while listing variables. * The pattern "\_s\zs" matches at EOL. * Trying every character position for a match is inefficient. * Eclipse preference files are not recognized. * Part of making search more efficient is missing. OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=764
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>