8d814e00f1
* Compilation problems on HP_nonStop (Tandem).
* Inconsistency: ":sp foo" does not reload "foo", unless "foo" is
the current buffer. (Liang Li)
* Compiler warnings. (Tony Mechelynck)
* When src/auto/configure was updated, "make clean" would run
configure pointlessly.
* It's not easy to remove duplicates from a list.
* When 'relativenumber' or 'cursorline' are set the window is
redrawn much to often. (Patrick Hemmer, Dominique Pelle)
* Test 105 does not work in a shadow dir. (James McCoy)
* Quickfix doesn't resize on ":copen 20". (issue 199)
* The Ruby directory is constructed from parts.
* Still using an older autoconf version.
* /usr/bin/grep on Solaris does not support -F.
* Dynamic Ruby doesn't work on Solaris.
* Cursurline highlighting not redrawn when scrolling. (John
Marriott)
* Can't build with Ruby 1.8.
* Compiler warnings when building with Python 3.2.
* Using ":let" for listing variables and the second one is a curly
braces expression may fail.
* Error when using ":options".
* An error in ":options" is not caught by the tests.
* ":%s/\n//" uses a lot of memory. (Aidan Marlin)
* Escaping special characters for using "%" with a shell command is
inconsistant, parenthesis are escaped but spaces are not.
* Can't get the command that was used to start Vim.
* It is not easy to get the full path of a command.
* It's not that easy to check the Vim patch version.
OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=209
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>