On Fri, Oct 25, 2019 at 4:05 AM Sihera Andre <[email protected]> wrote: > > Tony, > Christian, > Sorry for the delayed response. > > On 24/10/2019 11:07, Tony Mechelynck wrote: > > > > Runtime files ought to be of a version as close as possible to the > > executable with which they are used. Using 8.0 runtime files with a > > 8.1 executabe might work — or it might not. > > > > > Up until now I have always built the HEAD version and it has > worked fine against previous run-times. As a sanity check, I > checked out version 8.0.1766 of the source code (i.e., the > version that matches the run-time in the repository as > opposed to HEAD) and built it locally. Lo and behold, the > error disappeared. > > Thanks for the suggestion. > > > On 24/10/2019 15:19, Christian Brabandt wrote: > > With patch 8.1.0112 Vim will throw an error, if the `skip` argument for > > the searchpair() function is not a string argument while previously Vim > > did ignore this error. This means the matchparen plugin needs to be > > updated to fix this bug. > > > > <snip> > > > > Best, > > Christian > Thanks for this information. > > So the "matchparen" plugin on my end (run-time v8.0.1766) is > old and broke with the code fix in patch 8.1.0112. Understood. > > Is there a HEAD version of the run-time I can download to match > the HEAD version of the source tree? Or will I have to wait until > the repositories are next updated? > > Cheers, > > Andre.
1. Clone the repository (either the git repository or the Mercurial mirror, they should give you the same source tree). 2. I assume you aren't interested in building several versions of Vim with different configure arguments. 3. Set up a script to be sourced by your shell in order to set the configure settings appropriately. http://users.skynet.be/antoine.mechelynck/vim/compunix.htm has an example for the bash shell. Modify it as needed. At least the "compiled-by" will need to be changed, possibly other lines. /!\ Your shell should *source* this script, not *execute* it. 4. Run "make config" in the vim or vim/src directory of your clone. This will prepare the configure files according to your wishes _and_ to what software is instaled on your machine. You should log the output and chek it. If it's OK: 5. Run "make" in the same directory. This should build a Vim executable and put it in the vim/src directory of your clone. 6. Run "make install". This will install the executable you just built (stripping the result), normally into /usr/local/bin/. It will also install the corresponding runtime files, normally under /usr/local/share/vim/vim81/. 7. I expect "make install" to create (the first ime) a number of symllinks to your new executable, but if it didn't you may create them manually as folows (assuming your Vim is GUI-enabled): pushd /usr/local/bin ln -sv vim eview ln -sv vim evim ln -sv vim ex ln -sv vim gview ln -sv vim gvim ln -sv vim gvimdiff ... (etc. for the executable names found at ":help ex") popd Beware that the ln utilty wants the target first and the link name afterwards, which I find counterintuitive. Adding the -v (verbose) switch, as above, lets you check that it created the links the way you wanted them. When there are source changes, you can then update your clone, make sure your configuration arguments areset in the environment as with 3 above, and run make followed by make install as in 5 and 6 above. (No need to reconfigure.) This will rebuild only the changed modules. If you want to change your configuration arguments, edit the script to set your environment differently, then run "make reconfig" instead of "make". This will rerun configure and recompile everything from scratch. Then run "make install" as above. The "make install" step will not only install the executable in the $PATH where it belongs, it will also install the _corresponding_ runtime files (from the vim/runtime/ directory of your clone) where that executable will expect them. When you run Vim, $VIM and $VIMRUNTIME should not be set outside of Vim, it will set them appropriately (usually to /usr/local/share/vim and /usr/local/share/vim/vim81 respectively; if and when Vim 8.2 gets released it will set $VIMRUNTIME to something ending in …/vim82 instead). Best regards, Tony. -- -- 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 Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAJkCKXtmjQ2meyopzmhj8%2BgiYQXUBa4Tpf_B12XYUBj_XB5Q5Q%40mail.gmail.com.
