d614f5a310
- vim-changelog.sh: * use https:// URL for authenticity. For this URL needs to be changed to nluugl.nl which is the actual server behind this and the SSL certificate only works for this URL. * Check for number of arguments. * Maintain leading zeroes in version arguments, otherwise things like `vim-changelog.sh 0007 0010` fail to work. OBS-URL: https://build.opensuse.org/request/show/876001 OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=651 |
||
---|---|---|
.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>