Saluton Mr.SpOOn :)

Mr.SpOOn <[email protected]> skribis:
> Raúl Núñez de Arenas Coronado wrote:
>>Tricky. Unless you really HATE some option (or support) that came with
>>one of the "flavors" of VIM (tiny, small, big, huge), I strongly
>>recommend you to stick to one of these. Probably a "big" version will
>>be enough for you. In any case, ":help feature-list" and ":help
>>install" within a running Vim.
>>
>>I may have not mentioned it: STICK TO ONE OF THE BASICS "FLAVORS" of
>>Vim if you can live with it. It is much easier and you can rebuild
>>when you are an expert in enabling and disabling features (some of
>>them depend on others, so it is a bit tricky to get only what you
>>want).
>
> My problem was quite the opposite. I don't want to miss some cool
> option :D

;) Well, then you can use a "huge" version and fine tune the
configuration. It is not the easiest thing on Earth, though. And
remember: some features depend on other features, so you may not be able
to remove certain things you are not going to use if you use others.

At first I did just like you, trying to fine tune the precise config I
wanted for building Vim, but later I noticed that using a "huge" version
without GUI, with Perl and Python was exactly what I wanted and required
less work. This means I have some feature I don't want, but removing it
would be more complex and I won't be gaining anything, really.

> 2009/11/23 Frank Shute <[email protected]>:
>> Is there any particular reason you want to compile and not install a
>> package from one of the Ubuntu repositories?
>
> It's been a while since last time I compiled Vim, so I'm not really
> sure, but I was using some plugin that required a newer vim versione.
> Maybe it was netrw.

Ubuntu Vim is, usually, quite old. This is not Ubuntu's fault, exactly,
it's because Vim is very alive in terms of development, and patches are
produced very fast. This is good, because bugs doesn't live long!
Before, I used Ubuntu's Vim. Now I prefer to build my own. It's the only
app I build nowadays (some time ago I didn't use a distro, so I built
all my software).

> Well, there are archives to download them easier, so that would not be
> a problem. The problem would be to patch them all. I shall write a
> script for that. I was just wondering if I had to download all of
> them.

rsync will download only new patches (see Tony's instructions for that),
and after that I recommend that you ALWAYS build from pristine sources.
That is, extract the tarballs and apply ALL patches again. This is fast
and saves you from having to track which patches you already applied.
And if you, like me, like to build different versions at times, tweaking
the sources, etc. it's better to build from scratch, just in case.

-- 
Raúl "DervishD" Núñez de Arenas Coronado
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to