df204095ab
Updated to version 8.2.2411, fixes the following problems
* Debugging code included.
* Some test files may not be deleted.
* Not all ways Vim can be started are tested.
* Vim9: crash when using :trow in a not executed block.
* Vim9: wrong error when modifying dict declared with :final.
* Vim9: missing :endif not reported when using :windo.
* Vim9: warning for uninitialized variable. (Tony Mechelynck)
* Pascal-like filetypes not always detected.
* Vim9: "silent return" does not restore command modifiers.
* Vim9: it is not possible to extend a dictionary with different item types.
* Configure test for GTK only says "no". (Harm te Hennepe)
* Vim9: no error if using job_info() result wrongly.
* Cannot get the type of a value as a string.
* win_execute() unexpectedly returns number zero when failing.
* Expression command line completion shows variables but not functions after
"g:". (Gary Johnson)
* "char" functions return the wront column in Insert mode when the cursor
is beyond the end of the line.
* Vim9: return type of readfile() is any.
* Using inclusive index for slice is not always desired.
* No focus events in a terminal.
* Codecov reports every little coverage drop.
* Build failure without GUI.
* No check for modified files after focus gained. (Mathias Stearn)
* Vim9: cannot handle line break after parenthesis at line end.
* Using "void" for no reason.
* Vim9: error message for "throw" in function that was called with "silent!".
* If the focus lost/gained escape sequence is received twice it is not
ignored. (Christ van Willigen)
* Spartql files are not detected.
* Crash with a weird combination of autocommands.
* Stray test failure on Appveyor.
* Vim9: ":put =expr" does not handle a list properly.
* Vim9: crash when parsing function return type fails.
* Wrong #ifdef for use_xterm_like_mouse().
* Strange test failure with MS-Windows.
* Test leaves file behind.
* Vim9: no highlight for "s///gc" when using 'opfunc'.
* Vim9: check of builtin function argument type is incomplete.
* Vim9: line break in lambda accesses freed memory.
* Vim9: no check for map() changing item type at script level.
* When using ":sleep" the cursor is always displayed.
* Test failures on some less often used systems.
* Insufficient tests for setting options.
* Vim9: functions return true/false but can't be used as bool.
* Vim9: command fails in catch block.
* Vim9: crash when using types in :for with unpack.
* Confusing error message for wrong :let command.
* Vim9: list assignment only accepts a number index.
* Accessing uninitialized memory in test_undo.
* Test for RGB color skipped in the terminal.
* Vim9: crash when dividing by zero in compiled code using constants.
* Vim9: crash when using a range after another expression.
* Vim9: no error message for dividing by zero.
* Finding spell suggestions twice if 'spellsuggest' contains number.
* Vim9: occasional crash when using try/catch and a timer.
* Vim9: divide by zero does not abort expression execution.
* Build failure.
* Focus escape sequences are not named in ":set termcap" output.
* Turtle filetype not recognized.
* "gj" and "gk" do not work correctly when inside a fold.
* Vim9: crash when using ":silent! put".
* Runtime type check does not mention argument index.
* No easy way to get the maximum or mininum number value.
* Test failure on a few systems.
* Vim9: using positive offset is unexpected.
* Memory leak when creating a global function with closure.
* Fennel filetype not recognized.
* Vim9: error message when script line starts with "[{".
* Vim9: min() and max() return type is "any".
* Vim9: error for wrong type may report wrong line number.
* Vim9: no white space allowed before "->".
* Vim9: "%%" not seen as alternate file name for commands with a buffer
name argument.
* Method test fails.
* Fold test fails in wide terminal.
* Vim9: compiled functions are not profiled.
* Build fails without +profiling feature.
* Some filetypes not detected.
* Vim9: profiling if/elseif/endif not correct.
* Vim9: profiling try/catch not correct.
* Vim9: no need to allow white space before "(" for :def.
* Vim9: profiled :def function leaks memory.
* Old jumplist code is never used.
* MinGW: "--preprocessor" flag no longer supported.
* Vim9: profiling only works for one function.
* Build failure without the +profiling feature.
* Profile test fails on MS-Windows.
OBS-URL: https://build.opensuse.org/request/show/867401
OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=646
|
||
|---|---|---|
| .gitattributes | ||
| .gitignore | ||
| apparmor.vim | ||
| disable-unreliable-tests.patch | ||
| gvim_24.png | ||
| gvim_32.png | ||
| gvim_48.png | ||
| gvim_64.png | ||
| gvim_96.png | ||
| gvim.desktop | ||
| gvim.svg | ||
| no-common.patch | ||
| README.Japanese-XIM | ||
| spec.skeleton | ||
| spec.vim | ||
| suse.gvimrc | ||
| suse.vimrc | ||
| vim73-no-static-libpython.patch | ||
| vim132 | ||
| vim-7.3-filetype_changes.patch | ||
| vim-7.3-filetype_ftl.patch | ||
| vim-7.3-filetype_spec.patch | ||
| vim-7.3-gvimrc_fontset.patch | ||
| vim-7.3-help_tags.patch | ||
| vim-7.3-mktemp_tutor.patch | ||
| vim-7.3-name_vimrc.patch | ||
| vim-7.3-sh_is_bash.patch | ||
| vim-7.3-use_awk.patch | ||
| vim-7.4-disable_lang_no.patch | ||
| vim-7.4-filetype_apparmor.patch | ||
| vim-7.4-filetype_mine.patch | ||
| vim-7.4-highlight_fstab.patch | ||
| vim-7.4-rpmlintrc | ||
| vim-8.0-ttytype-test.patch | ||
| vim-8.0.1568-defaults.patch | ||
| vim-8.1.0297-dump3.patch | ||
| vim-8.2.2411.tar.gz | ||
| vim-changelog.sh | ||
| vim.changes | ||
| vim.spec | ||
| vimrc_example1 | ||
| vimrc_example2 | ||
| vitmp.1 | ||
| vitmp.c | ||
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>