2be7922523
* The cursor report sequence is sometimes not recognized and results in entering replace mode. * Mercurial picks up some files that are not distributed. * When repeating a filter command "%" and "#" are expanded. * Visual block mode plus virtual edit doesn't work well with tabs. (Liang Li) * ":lu" is an abbreviation for ":lua", but it should be ":lunmap". (ZyX) * Now that the +visual feature is always enabled the #ifdefs for it are not useful. * It's not possible to open a new buffer without creating a swap file. OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=206 |
||
---|---|---|
.gitattributes | ||
.gitignore | ||
apparmor.vim | ||
gvim.desktop | ||
missing-vim-client | ||
README.Japanese-XIM | ||
spec.skeleton | ||
suse.gvimrc | ||
suse.vimrc | ||
vim73-no-static-libpython.patch | ||
vim132 | ||
vim-7.1.314-CVE-2009-0316-debian.patch | ||
vim-7.3-diff_check.patch | ||
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-patches.tar.bz2 | ||
vim-7.4-rpmlintrc | ||
vim-7.4.tar.bz2 | ||
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>