b9d1bfac17
* Compiler warning.
* In the terminal the scroll wheel always scrolls the active window.
* Ruby 2.0 has a few API changes.
* "xxd -i" fails on an empty file.
* Clipboard does not work on Win32 when compiled with Cygwin.
* Empty lines in :version output when 'columns' is 320.
* Insufficient testing for mksession.
* Some files missing in the list of distributed files.
* "\@<!" in regexp does not work correctly with multi-byte
characters, especially cp932.
* When a "cond ? one : two" expression has a subscript it is not
parsed correctly. (Andy Wokula)
* Compiler warning for signed/unsigned pointer.
* Missing test file changes.
* Enum is not indented correctly with "public" etc.
* Enum indenting is not tested.
* Missing proto file, listing a non-existing proto file.
* Test 55 fails when messages are translated.
* Can't build with Ruby 2.0 when using MinGW x64 or MSVC10.
* ":g//" gives "Pattern not found error" with E486. Should not use
the error number, it's not a regular error message.
* ":vimgrep //" matches everywhere.
* Using an empty pattern with :sort silently continues when there is
no previous search pattern.
* system() breaks clipboard text. (Yukihiro Nakadaira)
* Using "ra" in multiple lines on multi-byte characters leaves a few
characters not replaced.
* After using backspace in insert mode completion, CTRL-N and CTRL-P
do not highlight the right entry. (Olivier Teuliere)
OBS-URL: https://build.opensuse.org/package/show/editors/vim?expand=0&rev=132
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>