c8aeb87930
- Updated to revision 580, fixes the following problems
* Ex range handling is wrong for buffer-local user commands.
* Segfault with wide screen and error in 'rulerformat'. (Ingo Karkat)
* No test for replacing on a tab in Virtual replace mode.
* FEAT_OSFILETYPE is used even though it's never defined.
* Ranges for arguments, buffers, tabs, etc. are not checked to be
valid but limited to the maximum. This can cause the wrong thing
to happen.
* :argdo, :bufdo, :windo and :tabdo don't take a range.
* Non-ascii vertical separater characters are always redrawn.
* Giving an error for ":0wincmd w" is a problem for some plugins.
* Having CTRL-C interrupt or not does not check the mode of the
mapping. (Ingo Karkat)
* Building with dynamic library does not work for Ruby 2.2.0
* Can't build with tiny features. (Ike Devolder)
* Address type of :wincmd depends on the argument.
* Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat)
* No error for eval('$').
* Unicode character properties are outdated.
* Redrawing problem with 'relativenumber' and 'linebreak'.
* Matching with a virtual column has a lot of overhead on very long
lines. (Issue 310)
* Using getcurpos() after "$" in an empty line returns a negative
number.
* Wrong cursor positioning when 'linebreak' is set and lines wrap.
* ":52wincmd v" still gives an invalid range error. (Charles
Campbell)
OBS-URL: https://build.opensuse.org/request/show/281394
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/vim?expand=0&rev=147
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>