I read ":help packages" and ":help add-package", trying to get a
better understanding of how this all works, and had a few comments.
Vim version is 7.4.1655.
* repeat.txt, line 484
Note that the files under "pack/foo/opt" or not loaded automatically,
only the
The "or" should be "a
Hi Bram and list,
I wrote another improved patch for the help tagjump.
If tag contains ({ or ([, Tag is set to terminate the (
It will not require a space after the "function_name(" in the help.
Please include this.
--
Best regards,
Hirohito Higashi (a.k.a. h_east)
--
--
You received this mes
Hi Bram,
I rewrote a patch and added a test.
This issue is in the TODO list.
TODO> Patch to have better check for {action} argument of setqflist().
TODO> Nikolai Pavlov, Feb 25, #661. Can be even more strict.
TODO> Also see patch from Hirohito Higash, Feb 25.
Please include this.
--
Best regards
Hi list and Benji,
2016/3/18 Fri 20:18:18 UTC+9 Ken Takata wrote:
> The matchit plugin doesn't respect the 'matchpairs' option sometimes.
> E.g. When editing an html file, cannot jump between a pair of parentheses
> with %.
>
> Attached patch fixes the problem. The basic idea is came from tmhedb
On 2016-03-25, Bram Moolenaar wrote:
> Gary Johnson wrote:
>
> > On 2016-03-25, Bram Moolenaar wrote:
> > > Patch 7.4.1649
> > > Problem:The matchit plugin needs to be copied to be used.
> > > Solution: Put the matchit plugin in an optional package.
> > > Files: Filelist, runtime/macros
Charles Campbell wrote:
> Vim builds, though, so I get 7.4.1583. I don't use it as it still hangs
> with pchk (http://www.drchip.org/astronaut/vim/index.html#PCHK), ever
> since patch#866.
Perhaps 7.4.1655 fixes that.
--
"Microsoft is like Coke. It's a secret formula, all the money is from
d
Ramel wrote:
> I compiled the latest version (7.4.1643) and found that remote_expr()
> function is not working. I can use --remote-expr command line argument
> successfully but not the corresponding function:
>
> $ gvim -u NONE --servername FOOBAR
> $ gvim -u NONE
>
> In the last Vim instance
Patch 7.4.1655
Problem:remote_expr() hangs. (Ramel)
Solution: Check for messages in the waiting loop.
Files: src/if_xcmdsrv.c
*** ../vim-7.4.1654/src/if_xcmdsrv.c2016-01-30 17:24:01.802502407 +0100
--- src/if_xcmdsrv.c2016-03-25 18:58:51.027437786 +0100
***
*** 606
Patch 7.4.1654
Problem:Crash when using expand('%:S') in a buffer without a name.
Solution: Don't set a NUL. (James McCoy, closes #714)
Files: src/eval.c, src/testdir/test_fnamemodify.vim
*** ../vim-7.4.1653/src/eval.c 2016-03-25 15:40:45.928372939 +0100
--- src/eval.c 2016-03-25 18
Gary Johnson wrote:
> On 2016-03-25, Bram Moolenaar wrote:
> > Patch 7.4.1649
> > Problem:The matchit plugin needs to be copied to be used.
> > Solution: Put the matchit plugin in an optional package.
> > Files: Filelist, runtime/macros/matchit.vim,
> > runtime/macros/matchit.txt,
> >
Patch 7.4.1653 (after 7.4.1649)
Problem:Users who loaded matchit.vim manually have to change their
startup. (Gary Johnson)
Solution: Add a file in the old location that loads the package.
Files: runtime/macros/matchit.vim, Filelist
*** ../vim-7.4.1652/runtime/macros/matchi
Hi Gary and Bram,
2016/03/26 1:32 "Gary Johnson" :
>
> I never copied the matchit plugin, as that would have prevented me
> from automatically picking up changes to it. Instead, I created the
> file ~/.vim/plugin/matchit.vim containing this line:
>
> runtime macros/matchit.vim
>
> What is the
Patch 7.4.1652
Problem:Old style test for fnamemodify().
Solution: Turn it into a new style test.
Files: src/testdir/test105.in, src/testdir/test105.ok,
src/testdir/test_fnamemodify.vim, src/testdir/test_alot.vim,
src/testdir/Make_all.mak
*** ../vim-7.4.1651/sr
On 2016-03-25, Bram Moolenaar wrote:
> Patch 7.4.1649
> Problem:The matchit plugin needs to be copied to be used.
> Solution: Put the matchit plugin in an optional package.
> Files: Filelist, runtime/macros/matchit.vim, runtime/macros/matchit.txt,
> runtime/macros/README.txt,
Ken Takata:
> MS-DOS support was removed with 7.4.1399, but we can remove some more #ifdefs
> from misc1.c. ("#ifdef WIN3264" is nested.)
> Please check the attached patch.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
120. You ask a friend, "What's that big shiny thing?" He
Patch 7.4.1651
Problem:Some dead (MSDOS) code remains.
Solution: Remove the unused lines. (Ken Takata)
Files: src/misc1.c
*** ../vim-7.4.1650/src/misc1.c 2016-03-19 22:11:47.424674965 +0100
--- src/misc1.c 2016-03-25 17:19:12.072192268 +0100
***
*** 9737,9754
re
Manuel Ortega wrote:
> I just tried to build 7.4.1648. "make test" failed thus:
>
> ===8<==
> Test results:
>
> >From test_quickfix.vim:
> Found errors in Test_caddbuffer_to_empty():
> function RunTheTest[9]..Test_caddbuffer_to_empty line 4: command did not
> fail: cn
> TEST FAILUR
I just tried to build 7.4.1648. "make test" failed thus:
===8<==
Test results:
>From test_quickfix.vim:
Found errors in Test_caddbuffer_to_empty():
function RunTheTest[9]..Test_caddbuffer_to_empty line 4: command did not
fail: cn
TEST FAILURE
make[2]: *** [report] Error 1
make[1]: **
Patch 7.4.1650
Problem:Quickfix test fails.
Solution: Accept any number of matches.
Files: src/testdir/test_quickfix.vim
*** ../vim-7.4.1649/src/testdir/test_quickfix.vim 2016-03-25
15:01:06.984578229 +0100
--- src/testdir/test_quickfix.vim 2016-03-25 17:11:47.796706594 +
Patch 7.4.1649
Problem:The matchit plugin needs to be copied to be used.
Solution: Put the matchit plugin in an optional package.
Files: Filelist, runtime/macros/matchit.vim, runtime/macros/matchit.txt,
runtime/macros/README.txt, src/Makefile,
runtime/pack/dist/o
Hi,
MS-DOS support was removed with 7.4.1399, but we can remove some more #ifdefs
from misc1.c. ("#ifdef WIN3264" is nested.)
Please check the attached patch.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you ar
Patch 7.4.1648
Problem:Compiler has a problem copying a string into di_key[]. (Yegappan
Lakshmanan)
Solution: Add dictitem16_T.
Files: src/structs.h, src/eval.c
*** ../vim-7.4.1647/src/structs.h 2016-03-20 21:17:09.103456337 +0100
--- src/structs.h 2016-03-25 1
Yegappan Lakshmanan wrote:
> I built the latest vim (7.4.1646) with debug (-g) information on Mac OS.
> On startup, Vim aborts at the following location:
>
> frame #7: 0x00010002fe23 vim`eval_init + 163 at eval.c:940
>937 for (i = 0; i < VV_LEN; ++i)
>938 {
>939
Dominique wrote:
> afl-fuzz found another use of free memory in
> Vim-7.4.1646 and older in quickfix.c.
>
> Steps to reproduce:
>
> $ cat crash.vim
> helpgr quickfix
> call setqflist([], 'r')
> cad
> cn
>
> $ vim -u NONE -S crash.vim
> Vim: Caught deadly signal SEGV
>
> Vim: Finished.
> Segme
Patch 7.4.1647
Problem:Using freed memory after setqflist() and ":caddbuffer". (Dominique)
Solution: Set qf_ptr when adding the first item to the quickfix list.
Files: src/quickfix.c, src/testdir/test_quickfix.c
*** ../vim-7.4.1646/src/quickfix.c 2016-03-23 20:55:22.823036742 +0
Hi all,
I built the latest vim (7.4.1646) with debug (-g) information on Mac OS.
On startup, Vim aborts at the following location:
frame #7: 0x00010002fe23 vim`eval_init + 163 at eval.c:940
937 for (i = 0; i < VV_LEN; ++i)
938 {
939p = &vimvars[i];
-> 940
the problem has disappeared, thanks.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Go
Hi rameo,
2016/3/25 Fri 19:06:47 UTC+9 rameo wrote:
> I've downloaded the latest vim release here:
> https://sourceforge.net/projects/cream/files/Vim/
> 7.4.1641 is still connected with python 3.3
>
> But this one at
> https://github.com/vim/vim-win32-installer/releases
> 7.4.1641 is connected w
Hi
afl-fuzz found another use of free memory in
Vim-7.4.1646 and older in quickfix.c.
Steps to reproduce:
$ cat crash.vim
helpgr quickfix
call setqflist([], 'r')
cad
cn
$ vim -u NONE -S crash.vim
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)
Valgrind says:
==
Ken,
I've downloaded the latest vim release here:
https://sourceforge.net/projects/cream/files/Vim/
7.4.1641 is still connected with python 3.3
But this one at
https://github.com/vim/vim-win32-installer/releases
7.4.1641 is connected with python 3.4
What is the difference between both releases?
Hi Rodolfo,
2016-3-25(Fri) 9:05:23 UTC+9 Rodolfo Borges:
> It works fine in neovim. Just saying :}
Neovim is installed matchit.vim by default.
Vim is not.
It's just the difference.
Please see the document.
:h matchit-install
Someday, I'll improve the implementation of the C source code of findm
31 matches
Mail list logo
