48ffb7c69a
- Updated to version 9.0.1894, fixes the following problems
- drop patches: disable-unreliable-tests.patch
ignore-flaky-test-failure.patch
vim-8.1.0297-dump3.patch
- fixes:
+ boo#1214922 - CVE-2023-4738
+ boo#1214925 - CVE-2023-4734
+ boo#1214924 - CVE-2023-4735
+ boo#1214921 - CVE-2023-4751
- droped %check - most of tests didn't work correctly in OBS
and maitenace burden of this was getting too big
* Not all cabal config files are recognized.
* Duplicate code for converting float to string.
* Message is cleared when removing mode message (Gary Johnson).
* Error message is cleared when removing mode message.
* Expanding a pattern interferes with command line completion.
* Compiler warning for uninitialized variable.
* crypt tests hang and cause memory errors
* Build failure without the crypt feature.
* Compiler warning for unused variables without the crypt feature.
* The log file does not give information about window sizes.
* Build failure with tiny features.
* Filetype detection fails if file name ends in many '~'.
* Not all filetype file name matches are tested.
* zserio files are not recognized.
* Insufficient testing for syntax plugins.
* Result of syntax tests is hard to see.
* Syntax test failure causes script to abort.
* Unclear why syntax test fails on Mac.
* Unclear why syntax test fails on Mac.
OBS-URL: https://build.opensuse.org/request/show/1110341
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/vim?expand=0&rev=353
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>