"Billy N. Patton" wrote:
> I've been using vim for several years now and have NEVER really looked at
> it's entire capabilities. I've looked through the FAQ's and help but I
> don't know what to search for or really to look for.
> After joining the mailing list I can see there may be possibilities to
> move to a much greater use of vim. I have a few questions/ramblings
> I currently support many(@30) of perl scripts and c programs that do QC of
> integrated circuit cell design. I often need to pop between each of these
> programs/scripts and edit/make/test/install.
> I use gvim (5.7) compiled with gtk mostly. Would it be possible
> to have a menu setup so that I could :
> 1. select a project from menu
> 2. have vim clear all buffers and return files to RCS.
> 3. have vim pull everything from RCS and load
> 4. auto save everything before make ( I just discovered how to put
> make and the error traversal on my function keys)
> 5. I know I can program function keys for the make test/install
> I suppose I could get the makefile to do the RCS checkin and checkout
> and have vim do a make checkout
> Ok if my makefile does the checkout/compile(if
> then vim would need to
> cd to specified directory (from pulldown menu)
> execute make checkout
> load N files into buffers
> and I don't have aclue as to how to get vim to do any of this, even if it
> I'm so confused :(
Think a little more about what you want vim to do and then we can
help you get it done. If you already know how to map function keys then
you basically know how to define menus: read
and you are there. If you can "execute make checkout" from vim's Command
line then you can program a menu item to do it.
I think the hard questions are
(1) How does vim decide what the list of projects is?
(2) How does vim decide what files to open for a given project?
For both questions, the simplest (but not the most convenient) answer is
that you maintain a file somewhere with the necessary information. If you
want a more automated approach, you have to decide where to get the
information. Are your "N files" all the *.cpp and *.h files in a given
Have a look at
as well. This may answer several of your questions.
HTH --Benji Fisher