Re: vimball, vundle vimplug compatibility

2018-02-04 0:12 GMT+03:00 Christian Brabandt : > > On Sa, 03 Feb 2018, Marc Weber wrote: > >> http://vam.mawercer.de/ >> You can add the plugins you want to the input and get the result as .zip >> for windows or linux. > > I have never had the need for that. When I used

Re: Patch 8.0.1458

On 2018-02-03, 21:35 GMT, Bram Moolenaar wrote: > I notice that "js" is another name for nodejs. I don't see > "js{version}", would one use that in a script shebang line? Probably not. I admit these scripts are quite rare (surprisingly), but I guess it can be alias to $DEFAULT_JS_INTEPRETER

Re: Patch 8.0.1458

Matěj Cepl wrote: > On 2018-02-03, 14:56 GMT, Bram Moolenaar wrote: > > + \ 'python': [['#!/path/python']], > > What about /usr/bin/python2 and /usr/bin/python3 We can check for those too. > > + \ 'javascript': [['#!/path/node'], > > + \['#!/path/nodejs'], >

Patch 8.0.1465

Patch 8.0.1465 Problem:Python2 and python3 detection not tested. (Matej Cepl) Solution: Add test for detecting python2 and python3. Also detect a script using "js" as javascript. Files: runtime/scripts.vim, src/testdir/test_filetype.vim ***

Re: vimball, vundle vimplug compatibility

On Sa, 03 Feb 2018, Marc Weber wrote: > http://vam.mawercer.de/ > You can add the plugins you want to the input and get the result as .zip > for windows or linux. I have never had the need for that. When I used vimballs, I downloaded them from vim.org opened them in Vim and was done. No need

Re: vimball, vundle vimplug compatibility

Ok it's a good reason I understand well and just see :RmVimball that is able to locate and remove LargeFile.vba I just installed. Without be pro or cons of existing or newer plugin manager, git linked to or not, just wonder why not to welcome all or no one. Was just a thought around that.

Re: vimball, vundle vimplug compatibility

http://vam.mawercer.de/ You can add the plugins you want to the input and get the result as .zip for windows or linux. vimball does not support dependencies. Yes its simple. True fix is cross language package manager, because sometimes you need dependencies for ruby or python. Marc Weber --

Re: vimball, vundle vimplug compatibility

On Sa, 03 Feb 2018, Marc Weber wrote: > Why is $vimruntime distributed with Vim? Because no-one likes an editor that has no syntax highlighting and all the other nice features of Vim that are not built into the C-core nowadays. And that is a good thing™ Christian -- Ernährt euch von Diäten!

Re: vimball, vundle vimplug compatibility

On Fr, 02 Feb 2018, Ni Va wrote: > Got a recent need to read Large Xml file, I think Large.vba from Charles E > Campbell is the best plugin > :http://www.drchip.org/astronaut/vim/index.html#LARGEFILE > > Then just wonder why vimball is integrated within vim distro and not others > plugin's

Patch 8.0.1464

Patch 8.0.1464 Problem:Completing directory after :find does not add slash. Solution: Adjust the flags for globpath(). (Genki Sky) Files: src/misc1.c, src/testdir/test_find_complete.vim *** ../vim-8.0.1463/src/misc1.c 2017-12-19 21:23:16.813960405 +0100 --- src/misc1.c 2018-02-03

Patch 8.0.1463

Patch 8.0.1463 Problem:Test fails without 'autochdir' option. Solution: Skip test if 'autochdir' is not supported. Files: src/testdir/test_autocmd.vim *** ../vim-8.0.1462/src/testdir/test_autocmd.vim2018-02-03 17:36:22.634091794 +0100 --- src/testdir/test_autocmd.vim

Re: vimball, vundle vimplug compatibility

You'll only become faster looking at the data you truly need. Nokogir will create a full ast. THere are event based XML parsers in some languages like Java or libxml vs expat (forgot) written in C https://stackoverflow.com/questions/4036659/what-are-fast-xml-parsers-for-ruby => SAX was one - but

Re: vimball, vundle vimplug compatibility

Hi Marc and thank you, I'd thought that runtime dir into https://github.com/vim/vim.git should be distributed up to date as compiled binary. For xml yes, I'm starting to deal with ruby nokogiri xml lib. I think it is fast but if you can advise on faster lib I will be glad. Just I wondered only

Patch 8.0.1462

Patch 8.0.1462 (after 8.0.1459) Problem:Missing yet another file in patch. Solution: Add changes to missing file. Files: src/gui.c *** ../vim-8.0.1461/src/gui.c 2018-01-31 21:09:57.631847554 +0100 --- src/gui.c 2018-02-03 16:12:25.887781704 +0100 *** *** 5528,5534

Re: Patch 8.0.1461

GVim can't be compiled after 1459 anymore, at least not on Windows: > gui.c(5531): error C2198: "vim_chdirfile": Nicht genügend Argumente > für Aufruf. I suspect that another file is missing... -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below

Patch 8.0.1461

Patch 8.0.1461 (after 8.0.1459) Problem:Missing another file in patch. Solution: Add changes to missing file. Files: src/ex_cmds.c *** ../vim-8.0.1460/src/ex_cmds.c 2017-12-09 21:10:09.610735718 +0100 --- src/ex_cmds.c 2018-02-03 17:13:48.248922716 +0100 ***

Re: Patch 8.0.1458

On 2018-02-03, 14:56 GMT, Bram Moolenaar wrote: > + \ 'python': [['#!/path/python']], What about /usr/bin/python2 and /usr/bin/python3 > + \ 'javascript': [['#!/path/node'], > + \['#!/path/nodejs'], > + \['#!/path/rhino']], /usr/bin/js and

Patch 8.0.1460

Patch 8.0.1460 (after 8.0.1459) Problem:Missing file in patch. Solution: Add changes to missing file. Files: src/misc2.c *** ../vim-8.0.1459/src/misc2.c 2017-12-22 21:03:04.866173775 +0100 --- src/misc2.c 2018-02-03 16:19:56.904146687 +0100 *** *** 3389,3401 *

Patch 8.0.1459

Patch 8.0.1459 Problem:Cannot handle change of directory. Solution: Add the DirChanged autocommand event. (Andy Massimino, closes #888) Avoid changing directory for 'autochdir' too often. Files: runtime/doc/autocmd.txt, src/buffer.c, src/ex_docmd.c,

Patch 8.0.1458

Patch 8.0.1458 Problem:Filetype detection test does not check all scripts. Solution: Add most scripts to the test Files: src/testdir/test_filetype.vim *** ../vim-8.0.1457/src/testdir/test_filetype.vim 2018-01-29 09:17:28.670732722 +0100 --- src/testdir/test_filetype.vim

Patch 8.0.1457

Patch 8.0.1457 Problem:Clojure now supports a shebang line. Solution: Detect clojure script from the shebang line. (David Burgin, closes #2570) Files: runtime/scripts.vim *** ../vim-8.0.1456/runtime/scripts.vim 2017-11-11 15:37:13.443209748 +0100 --- runtime/scripts.vim

Patch 8.0.1456

Patch 8.0.1456 Problem:Timer test on travis Mac is still flaky. Solution: Increase time range a bit more. Files: src/testdir/test_timers.vim *** ../vim-8.0.1455/src/testdir/test_timers.vim 2017-12-23 18:41:31.137791160 +0100 --- src/testdir/test_timers.vim 2018-02-03

Patch 8.0.1455

Patch 8.0.1455 Problem:If $SHELL contains a space then the default value of 'shell' is incorrect. (Matthew Horan) Solution: Escape spaces in $SHELL. (Christian Brabandt, closes #459) Files: src/option.c, runtime/doc/options.txt, src/testdir/test_startup.vim

Patch 8.0.1454

Patch 8.0.1454 Problem:When in silent mode too much output is buffered. Solution: Use line buffering instead of fully buffered. (Brian M. Carlson, closes #2537) Files: src/main.c *** ../vim-8.0.1453/src/main.c 2018-01-31 20:51:40.305835913 +0100 --- src/main.c

Re: vimball, vundle vimplug compatibility

Why is $vimruntime distributed with Vim? Eg the error format plugin of me does only one job, while :compiler of Vim is doing too much IMHO .. http://github.com/MarcWeber/vim-addon-errorformats Why not share code between Vim & Emacs & vscode & ..? This is an attempt to see where it goes:

Re: vimball, vundle vimplug compatibility

On 2018-02-03, 00:35 GMT, Ni Va wrote: > Then just wonder why vimball is integrated within vim distro > and not others plugin's managers like vimplug > : https://github.com/junegunn/vim-plug.git https://shapeshed.com/vim-packages/ (put your ~/.vim in a git repo, then those plugins could be git