215dd177e2
* GTK: font glitches for combining characters * "zt" still doesn't work well with filler lines. (Gary Johnson) * Dragging the current tab with the mouse doesn't work properly. * It's a bit clumsy to execute a command on a list of matches. * Vim doesn't recognize all htmldjango files. * Filetype detection is outdated. * pango_shape_full() is not always available. * Still problems with pango_shape_full() not available. * plines_nofill() used without the diff feature. OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=285 |
||
|---|---|---|
| .gitattributes | ||
| .gitignore | ||
| apparmor.vim | ||
| gvim.desktop | ||
| gvim.svg | ||
| missing-vim-client | ||
| README.Japanese-XIM | ||
| spec.skeleton | ||
| suse.gvimrc | ||
| suse.vimrc | ||
| v7.4.865.tar.gz | ||
| 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-rpmlintrc | ||
| 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>