On Fr, 16 Sep 2016, boB Stepp wrote:
> On Fri, Sep 16, 2016 at 5:04 AM, Christian Brabandt <cbli...@256bit.org>
> > On Mi, 14 Sep 2016, boB Stepp wrote:
> >> On Wed, Sep 14, 2016 at 2:08 AM, Christian Brabandt <cbli...@256bit.org>
> >> wrote:
> >> > You can download 64bit versions from the nightly builds:
> >> > https://github.com/vim/vim-win32-installer
> >> > and here (non-official) builds:
> >> > https://tuxproject.de/projects/vim/
> >> I downloaded the self-extracting package from the tuxproject link. So
> >> far all looks good. However, there is a cautionary comment on the
> >> page which reads:
> >> "You'll need to have the appropriate DLL files in your Vim directory
> >> or somewhere in your %PATH% to make them work. They're not included."
> >> Which DLL files are you referring to?
> > While the binary Vims distributed at the vim-win32-installer repository
> > are build to include the various scripting engines (python2.7/3, lua,
> > perl, etc), to make use of those features you need to install those
> > scripting engines separatly, else you won't be able to use any of those
> > features.
> That's what I was hoping you meant. One further question: If I
> should need a language that I am not currently using in the future,
> install the language AFTER I installed Vim, will Vim find the new
> language as long as I ensure the language's executable is included in
Yes I believe so.
Ein Volk kann nicht auf seine Genies, sondern auf das Volk, auf die
Menge stolz sein - die Genies können auf die Genies es sein.
-- Jean Paul
You received this message from the "vim_use" 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
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.