Patch 7.4.542
Problem:Using a range for window and buffer commands has a few problems.
Cannot specify the type of range for a user command.
Solution: Add the -addr argument for user commands. Fix problems. (Marcin
Szamotulski)
Files: src/testdir/test_command_cou
Marcin -
I think that we need to be more strict about window numbers. E.g., when
using "3close" while there are only two windows, should not close the
second window. This avoids mistakenly closing the wrong window.
If someone wanted to close the last window he should have used
":$close".
The s
Hirohito Higashi wrote:
> Hi Bram and Vim addicts,
>
> The multi-line regexp highlight regression occured from 7.4.405.
>
> How to reproduce #1.
> 1. Start vim.
> $ vim -N -u NONE
>
> 2. Input below.
> :call setline(1, repeat(['abc'], 3))
> :set hlsearch
> /bc\na
>
> Expect behavior:
Yukihiro Nakadaira wrote:
> In :help col() and virtcol(), "v" is not listed in the accepted positions.
Thanks, I'll include it.
--
|
Ceci n'est pas une pipe.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features --
Ozaki Kiichi wrote:
> I have made a testcase.
>
> test_nested_function.in
> https://gist.github.com/ichizok/267bae46f179d72b27dc
>
> test_nested_function.ok
> https://gist.github.com/ichizok/e4787725e785e839f4ec
Thanks!
--
Westheimer's Discovery:
A couple of months in the laboratory
I have made a testcase.
test_nested_function.in
https://gist.github.com/ichizok/267bae46f179d72b27dc
test_nested_function.ok
https://gist.github.com/ichizok/e4787725e785e839f4ec
Thank you.
- Ozaki Kiichi
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your r
Hi Bram and Vim addicts,
The multi-line regexp highlight regression occured from 7.4.405.
How to reproduce #1.
1. Start vim.
$ vim -N -u NONE
2. Input below.
:call setline(1, repeat(['abc'], 3))
:set hlsearch
/bc\na
Expect behavior:
1st line: bc is highlighted.
2nd line: abc is hig
On 22:41 Sat 06 Dec , Bram Moolenaar wrote:
>
> Marcin Szamotulski wrote:
>
> > On 09:32 Thu 04 Dec , Marcin Szamotulski wrote:
> > > On 14:31 Wed 03 Dec , Matteo Cavalleri wrote:
> > > > I'm using the code I posted a while ago in this thread, I'm copying it
> > > > here again :) (it
Hi James!
On Sa, 06 Dez 2014, James McCoy wrote:
> To top it off, I haven't yet found a way to make Vim re-realize it can
> talk to X, so basically vim (at least from the terminal) is completely
> cut off after that code is executed.
Indeed, I have also just recently (with the inclusion of patch
