Ondřej Súkup
93111e0f93
* Not all fields in "cstack" are initialized which might cause a crash. * Crash when using :all while using a cmdline window. (Zdenek Dohnal) * Using freed memory when closing the cmdline window. * No way to check for the cmdwin feature, cmdline_hist is now always enabled. * May get stuck in command line window state. * Condition stack values may be used when not set. * Color not changed if ModeMsg highlight is set in InsertEnter autocmd event. (Paul Swanson) * Autocmd test was failing on MS-Windows with GUI. * Too many problems with using all autocommand events. * Double free when using autocommand with "argdel". (Houyunsong) * Crash when deleting with line number out of range. (Houyunsong) * Missing error message. * Some tests are known to cause an error with ASAN. * Cursor on invalid line with range and :substitute. * Allowing 'completefunc' to switch windows causes trouble. * Can still switch windows for 'completefunc'. * FocusGained does not work when 'ttymouse' is empty. * :goto does not work correctly with text properties. (Sam McCall) * :vimgrep expands wildcards twice. * Warning for -fno-strength-reduce with Clang 11. * Libvterm tests are executed even when libtool doesn't work. * Opening cmdline window gives error in BufLeave autocommand. * Vim9: no error when compiling str2nr() with a number. * setline() gives an error for some types. * Vim9 script test is a bit flaky. * Deprecation warnings with default configuration. * Out of bounds compiler warning. OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=654 |
||
---|---|---|
.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-globalvimrc.patch | ||
vim-8.2.2564.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>