Thanks Tony/Benji,
Well I could not get the number to identify the script if at all any
given.
But on the script page it is mentioned as
" bufexplorer.zip : Easily switch between buffers without knowing their
numbers"
Author : jeff lanzarotta
Also, about installing vim 7.0
Will it be possible to install it in my working directory instead of root as
I won't be having the access to root.
Also, at present vim(6.4) is installed on the server, will it create any
clashes if two versions exists on the same server.
e.g. if I type command vim, will it take from <PATH>/vim64/bin...
or <PATH>/vim70/bin....
Further, can I use the GUI verion(gvim) if I'm working on windows PC and
using a terminal emulator(putty) to work on linux server.
~Regards~
Jagpreet
-----Original Message-----
From: A.J.Mechelynck [mailto:[EMAIL PROTECTED]
Sent: Monday, May 15, 2006 7:47 PM
To: [EMAIL PROTECTED]
Cc: 'Vim mailing list'
Subject: Re: issues..compilation,
jagpreet wrote:
> Hi There,
>
> I have recently installed vim 7.0 and also could never get a chance
earlier
> to use the compiler options in vim.
> I went through the document and set all the values but also could not
> compile the c/c++ file in vim window.
> Is there a clear document exists which explains how to use the compiler
> option in vim.
>
:help quickfix.txt
Is it "clear"? That is a matter of opinion. Like all vim docs, you may
need to read it attentively, and possibly several times over.
> What I understand so far is while editing the file we can compile it if
the
> proper compiler plugin is present in the plugin directory. Please correct
me
> if I'm wrong.
>
You can run a batch compile from vim if you have the proper :compiler
setting, 'makeprg' option, etc. Then you can inspect the errors (if any)
using quickfix commands.
>
> Also, I tried downloading the vim 7.0, linux version but could not get the
> downloadable as the link was broken. Is it available at any other place.
> I tried some mirrors also, but vim 6.4 is what the last stable version is
> the status.
>
ftp://ftp.vim.org/pub/vim/unix/vim-7.0.tar.bz2
ftp://ftp.vim.org/pub/vim/extra/vim-7.0-extra.tar.gz
ftp://ftp.vim.org/pub/vim/extra/vim-7.0-lang.tar.gz
and everything in
ftp://ftp.vim.org/pub/vim/patches/7.0/
These files taken together contain the full source and runtime files for
all supported OSs and languages.
I recommend the following (for Unix):
1. Create a directory ~/build/vim
2. Download all 3 archivesat any convenient place and uncompress them
there, on top of each other. They will create a tree structure starting
at ~/build/vim/vim70
3. Create a directory ~/build/vim/vim70/patches and download the full
contents of pub/vim/patches/7.0 there
4. The vim70 directory being current, run
patch -p0 < patches/7.0.001
patch -p0 < patches/7.0.002
etc., for all *new* patches in sequence. (If you have already compiled z
previous patchlevel ov Vim 7.0 release, you don't have to reapply the
older patches a second time.)
5. Inspect the file vim70/src/Makefile, make a note of whatever config
options you want to set, and create a batch script similar (not
necessarily identical) to this:
#!/bin/bash
export CONF_OPT_PERL='--enable-perlinterp'
export CONF_OPT_PYTHON='--enable-pythoninterp'
export CONF_OPT_TCL='--enable-tclinterp --with-tcl=tclsh8.4'
export CONF_OPT_RUBY='--enable-rubyinterp'
export CONF_OPT_MZSCHEME='--enable-mzschemeinterp'
export CONF_OPT_CSCOPE='--enable-cscope'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
export CONF_OPT_OUTPUT='--enable-fontset'
export CONF_OPT_FEAT='--with-features=huge'
export CONF_OPT_COMPBY='"[EMAIL PROTECTED]"'
6. In bash, source (with the "source" verb) the script you just created.
7. Run
make
followed by
make install
Between them, you can, for instance, run
src/vim --version
etc., to check that you got a working executable.
Note: if you change your configuration options, you will need to do
cd src
make reconfig
to override the previously "cached" configure settings.
To compile for Windows, see my
http://users.skynet.be/antoine.mechelynck/vim/compile.htm instead.
>
> Furthermore, I'm using plugin "bufexplorer.vim", but I'm not able to see
any
> window(extra buffer window, which was available in minibuf explorer).
> There is no screenshot available so I don't have much idea if works the
same
> way.
> When I use the command \mbe(or :BufferExplorer) as mentioned in the plugin
> document the error display is " E488: Trailing characters".
>
> Do I need to make some settings before using this plugin, though I have
> check the docs and no specific setting is mentioned in it, but no idea how
> to use this plugin.
>
> Regards
> Jagpreet
>
>
>
>
>
>
I don't know about the bufexpplorer plugin. In vim 7, "editing" a
dieectory should (with the standard netrw plugin) show a directory
listing, from which you can select which file to edit.
Best regards,
Tony.
