On Feb 3, 11:51 pm, pansz <[email protected]> wrote: > For this kind of use, the startup-time of vim is important, if, like > many average users who have no budget for a new personal computer or > their company refuses to upgrade their 5+-year-old computer, the > startup-time of vim varies. >
I have a computer at home that is now about 9 years old, with a startup time for HUGE Vim that is still faster than pretty much any other editor I've seen, except probably Notepad. It only takes a few seconds. > You want vim to start-up instantly, you customize your vim build. That's > quite straight forward. Many other software does not meet the situation, > because they don't typically launched by CLI and they will not be > enter/exit very often. > I think that most of Vim's startup time is in loading all the plugins and .vimrc customizations. If you want to limit startup time, I think your best bet is actually to simplify your user customizations. I don't have any hard numbers, but I know my normal gvim takes a few seconds to launch, whereas launching gvim -N -u NONE -i NONE happens pretty much instantly even with a huge build. > >> For advanced user like Matt, well, may have no difficulties identifying > >> distribution-specific vim directories. > > > Most people don't need to know that. > > Yes they did. A typical vim user may like using vim key-binding in most > CLI applications, especially they may like to have vim-style syntax > highlight for most files. e.g. using the macro included with vim to > replace the system pager. This script lies in > /usr/local/share/vim/vim72/macros/less.sh > > You'll have to know where your vim installed, before you can use the script. Compiling Vim yourself won't help you know where Vim is installed. I imagine most people install Vim with a simple: make config make make install Nowhere in this do you specify the install path, unless you really dig into the configuration. If I want to know Vim's install location, regardless of whether I compiled or not, I do: which vim If I want to know what scripts Vim loads, again regardless of whether I compiled it myself or not, I do :scriptnames. If I want to know where Vim looks for scripts, I do :set runtimepath?. The ONLY things I personally get from compiling Vim myself (not having modified the source by hand yet) are: 1. I can always have the absolute latest version 2. I can try out unofficial or unreleased bugfix patches if I want to -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
