Saturday, November 4, 2017

Re: vim versions

On Sat, Nov 4, 2017 at 1:47 PM, Renato Fabbri <renato.fabbri@gmail.com> wrote:
> I had a custom configuration file:
> https://github.com/ttm/vim/blob/master/Makefile
> which prevented git from performing pull.
> So it seems I am using the almost-bleeding edge.
>
> How often do you update your Vim version?

Whenever "hg incoming" (on Christian Brabandt's Mercurial mirror at
https://bitbucket.org/vim-mirror/vim) shows that there are new
changesets; however if all new changesets are for tests and/or
Windows, I download them but don't yet build (I'm on Linux and
normally I don't run the tests).
>
> Also, are there known teaks for dealing with the
> bleeding-edge or would you care to share yours?
> Here it works just fine with this vimrc:
> https://github.com/ttm/vim/blob/master/vimrc

I just uploaded my ~/.vimrc at
http://users.skynet.be/antoine.mechelynck/vim/vimrc — but I don't
regard it as specific to the latest development build; I would use it
with any "reasonably recent" build and with any featureset from Tiny
to Huge. It will ptobably not suit you as-is but if you see
interesting ideas in it, feel free to pick and choose.

I don't modify the Makefile, I use the src/Makefile unchanged and I
set my configure arguments by means of environment variables, see
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm


Best regards,
Tony.

--
--
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 "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: