Re: What plugin is the one that does the following ...
Andrew Falanga wrote: [...] You know, as I just recently noted to someone on the FreeBSD questions mailing list, I can't believe how much I don't know about vim, though I've been using it for several years now. Andy "The more I learn, and the more I am ignorant." -- Socrates Best regards, Tony. -- "What is the Nature of God?" CLICK...CLICK...WHIRRR...CLICK...=BEEP!= 1 QT. SOUR CREAM 1 TSP. SAUERKRAUT 1/2 CUT CHIVES. STIR AND SPRINKLE WITH BACON BITS. "I've just GOT to start labeling my software..." -- Bloom County
Re: What plugin is the one that does the following ...
On 4/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Quoting Andrew Falanga <[EMAIL PROTECTED]>:
> On 4/24/07, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote:
> > Andrew Falanga wrote:
> >
> > >
> > > Using your directions above, I continually get problems on step 4.
> > > when I so ":so %" I'm constantly returned "UseVimball" is not a vim
> > > command, or something similar. What might I be doing wrong?
> >
> >
> > Hmm, your original complaint was that netrw wasn't working at all, I
> > believe.
> >
> > Do you have something like the following at the beginning of your
> > <.vimrc> file?
> >
> > " =
> > " Initialize: {{{1
> > set nocp
> > if version >= 600
> > filetype plugin indent on
> > endif
>
> Actually, on this particular system, I have no ~/.vimrc file at all.
Without these commands, your vim is operating in "vi-compatible" mode, and
vi doesn't support plugins. Even with :set nocp, you need to enable plugins.
May I suggest trying the few lines above as your <.vimrc>, and then trying to
"edit" a directory.
Regards,
Chip Campbell
Dr. Chip,
Thank you for your help. As you've correctly noted, I needed those
things in my .vimrc file to make this all work. Incidentally, I found
I also had to add those lines to the .vimrc file for the root user (so
install the netrw package/plugin in the system wide
/usr/local/share/... location. Thanks again.
You know, as I just recently noted to someone on the FreeBSD questions
mailing list, I can't believe how much I don't know about vim, though
I've been using it for several years now.
Andy
Re: What plugin is the one that does the following ...
Quoting Andrew Falanga <[EMAIL PROTECTED]>:
> On 4/24/07, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote:
> > Andrew Falanga wrote:
> >
> > >
> > > Using your directions above, I continually get problems on step 4.
> > > when I so ":so %" I'm constantly returned "UseVimball" is not a vim
> > > command, or something similar. What might I be doing wrong?
> >
> >
> > Hmm, your original complaint was that netrw wasn't working at all, I
> > believe.
> >
> > Do you have something like the following at the beginning of your
> > <.vimrc> file?
> >
> > " =
> > " Initialize: {{{1
> > set nocp
> > if version >= 600
> > filetype plugin indent on
> > endif
>
> Actually, on this particular system, I have no ~/.vimrc file at all.
Without these commands, your vim is operating in "vi-compatible" mode, and
vi doesn't support plugins. Even with :set nocp, you need to enable plugins.
May I suggest trying the few lines above as your <.vimrc>, and then trying to
"edit" a directory.
Regards,
Chip Campbell
Re: What plugin is the one that does the following ...
Andrew Falanga wrote: On 4/24/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: Andrew Falanga wrote: >> It means step 2 wasn't done properly. You should find the unpacked >> vimball >> files in the plugin/ and autoload/ subfolders of some folder mentioned in >> 'runtimepath'. >> > > Nope, I looked in each of the directories (after doing tar -tf > vimball.tar, to get a list of the files), and all did extract > properly. > > Andy > Please use "Reply to All", nor "Reply to Sender" next time, so that other Vim users (including the plugin author, Dr. Charles "Chip" Campbell), can see your post. Sorry. I do have a hard time remembering. Will try to do better. ":UseVimball" is defined by the vimball plugin. If the vimball plugin files have been properly unpacked (and, maybe, you restarted Vim since then) then the ":scriptnames" command should show you that plugin/vimballPlugin.vim has been sourced. Ok, I did ":scriptnames" and I did see the plugin/vimballPlugin.vim as being sourced. However, I still get "E492: Not an editor command: UseVimball" when doing ":so %" as originally instructed by Dr. Chip. Andy - Are you sure the vimballPlugin.vim that is sourced is the one you just installed? - Are you sure another version of the same is not _also_ sourced? - Are you sure you don't create a variable named loaded_vimballPlugin (or g:loaded_vimballPlugin) in your vimrc? Best regards, Tony. -- To be is to do. -- I. Kant To do is to be. -- A. Sartre Yabba-Dabba-Doo! -- F. Flinstone
Re: What plugin is the one that does the following ...
On 4/24/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: Andrew Falanga wrote: >> It means step 2 wasn't done properly. You should find the unpacked >> vimball >> files in the plugin/ and autoload/ subfolders of some folder mentioned in >> 'runtimepath'. >> > > Nope, I looked in each of the directories (after doing tar -tf > vimball.tar, to get a list of the files), and all did extract > properly. > > Andy > Please use "Reply to All", nor "Reply to Sender" next time, so that other Vim users (including the plugin author, Dr. Charles "Chip" Campbell), can see your post. Sorry. I do have a hard time remembering. Will try to do better. ":UseVimball" is defined by the vimball plugin. If the vimball plugin files have been properly unpacked (and, maybe, you restarted Vim since then) then the ":scriptnames" command should show you that plugin/vimballPlugin.vim has been sourced. Ok, I did ":scriptnames" and I did see the plugin/vimballPlugin.vim as being sourced. However, I still get "E492: Not an editor command: UseVimball" when doing ":so %" as originally instructed by Dr. Chip. Andy
Re: What plugin is the one that does the following ...
Andrew Falanga wrote: It means step 2 wasn't done properly. You should find the unpacked vimball files in the plugin/ and autoload/ subfolders of some folder mentioned in 'runtimepath'. Nope, I looked in each of the directories (after doing tar -tf vimball.tar, to get a list of the files), and all did extract properly. Andy Please use "Reply to All", nor "Reply to Sender" next time, so that other Vim users (including the plugin author, Dr. Charles "Chip" Campbell), can see your post. ":UseVimball" is defined by the vimball plugin. If the vimball plugin files have been properly unpacked (and, maybe, you restarted Vim since then) then the ":scriptnames" command should show you that plugin/vimballPlugin.vim has been sourced. Best regards, Tony. -- Love means having to say you're sorry every five minutes.
Re: What plugin is the one that does the following ...
Andrew Falanga wrote: On 4/23/07, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote: 1) Get up-to-date versions of vimball and netrw: vimball: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimBall (the mysite.verizon.net one will be the more recent version) netrw: http://vim.sourceforge.net/scripts/script.php?script_id=1075 -or- http://mysite.verizon.net/astronaut/vim/index.html#NETRW 2) Remove the old vimball plugin and install the new one: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/vimball*.vim autoload/vimball*.vim doc/pi_vimball.txt mv (wherever it was downloaded)/vimball.tar.gz . gunzip vimball.tar.gz tar -xvf vimball.tar Windows: Under Windows, check your runtimepath to determine where your vim 7.0's runtime directories are: vim :echo &rtp :q The first directory is likely your personal plugins directory, the second one is your vim system directory. cd (to your vim system directory) del plugin\vimballPlugin.vim del autoload\vimball.vim del doc\pi_vimball.txt ren (wherever)\vimball.tar.gz vimball.tar.gz gunzip vimball.tar.gz tar -xvf vimball.tar 3) Remove system version of netrw: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/netrw*.vim autoload/netrw*.vim doc/pi_netrw.txt syntax/netrw*.vim Windows: cd (to your vim system directory) del plugin\netrwPlugin.vim del autoload\netrw.vim del doc\pi_netrw.txt del syntax\netrw.vim 4) Install an up-to-date version of netrw: vim netrw.vba.gz :so % :q Regards, Chip Campbell Dr. Chip, Using your directions above, I continually get problems on step 4. when I so ":so %" I'm constantly returned "UseVimball" is not a vim command, or something similar. What might I be doing wrong? andy It means step 2 wasn't done properly. You should find the unpacked vimball files in the plugin/ and autoload/ subfolders of some folder mentioned in 'runtimepath'. Best regards, Tony. -- ... So the documentary-makers stick with sharks. Generally, their procedure is to scatter bleeding fish pieces around their boat, so as to infest the waters. I would estimate that the primary food source of sharks today is bleeding fish pieces scattered by people making documentaries. Once the sharks arrive, they are generally fairly listless. The general shark attitude seems to be: "Oh God, another documentary." So the divers have to somehow goad them into attacking, under the guise of Scientific Research. "We know very little about the effect of electricity on sharks," the narrator will say, in a deeply scientific voice. "That is why Todd is going to jab this Great White in the testicles with a cattle prod." The divers keep this kind of thing up until the shark finally gets irritated and snaps at them, and then they act as though this was a totally unexpected and very dangerous development, although clearly it is what they wanted all along. -- Dave Barry, "The Wonders of Sharks on TV"
Re: What plugin is the one that does the following ...
On 4/23/07, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote: 1) Get up-to-date versions of vimball and netrw: vimball: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimBall (the mysite.verizon.net one will be the more recent version) netrw: http://vim.sourceforge.net/scripts/script.php?script_id=1075 -or- http://mysite.verizon.net/astronaut/vim/index.html#NETRW 2) Remove the old vimball plugin and install the new one: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/vimball*.vim autoload/vimball*.vim doc/pi_vimball.txt mv (wherever it was downloaded)/vimball.tar.gz . gunzip vimball.tar.gz tar -xvf vimball.tar Windows: Under Windows, check your runtimepath to determine where your vim 7.0's runtime directories are: vim :echo &rtp :q The first directory is likely your personal plugins directory, the second one is your vim system directory. cd (to your vim system directory) del plugin\vimballPlugin.vim del autoload\vimball.vim del doc\pi_vimball.txt ren (wherever)\vimball.tar.gz vimball.tar.gz gunzip vimball.tar.gz tar -xvf vimball.tar 3) Remove system version of netrw: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/netrw*.vim autoload/netrw*.vim doc/pi_netrw.txt syntax/netrw*.vim Windows: cd (to your vim system directory) del plugin\netrwPlugin.vim del autoload\netrw.vim del doc\pi_netrw.txt del syntax\netrw.vim 4) Install an up-to-date version of netrw: vim netrw.vba.gz :so % :q Regards, Chip Campbell Dr. Chip, Using your directions above, I continually get problems on step 4. when I so ":so %" I'm constantly returned "UseVimball" is not a vim command, or something similar. What might I be doing wrong? andy
Re: What plugin is the one that does the following ...
Gary Johnson wrote: On 2007-04-23, Andrew Falanga <[EMAIL PROTECTED]> wrote: On 4/23/07, Taylor Venable <[EMAIL PROTECTED]> wrote: Do you mean the ability to "edit" a directory and read its contents? yes The documentation says that it's distributed with vim. However, I installed vim using the FreeBSD ports system on my FreeBSD system and this pluglin, apparently, isn't installed along with the rest of vim. That's odd. The FreeBSD ports build method for Vim is simply to download the patches, apply them, and do a standard build. To my knowledge, nothing is removed. One possibility I can think of: did you build a "LITE" version? (Using `make -DLITE install` for example.) What leads you to believe that this functionality isn't present? Do you get some sort of error messages when you try to do something? Every time I do something like, "gvim ." or "vim .", when vim loads on the bottom of the screen I get ". is a directory" and there's nothing in the window to actually "edit." I did do some searching on the install I did. I did not do a "-lite" version in the ports tree. I did my install from /usr/ports/editors/vim (there's a .../vim-lite in the same directory of editors). I also found the netrw plugin referenced by Chip to exist in /usr/local/share/vim/vim70/plugin. According to what I've been able to determine, this should be sourced by vim when vim is executed. However, try as I have to remember, I do not recall the command to list the files vim sourced on startup. Can you provide that for me? :scriptnames Make sure you have a _current_ version of the netrw plugin and that you have installed it according to Dr. Chip's instructions (earlier in this thread). Depending on the versions of the runtime files you originally installed, it may not be sufficient to download and install netrw.vba--you may also have to disable the current netrw files under the $VIMRUNTIME directory. I install vim on a variety of different machines and every now and then I forget to properly update netrw. When I do, the symptoms are as you describe. Regards, Gary Downloading the patches is enough for the Vim binary. It is, however, usually not enough for the runtime files, because runtime file upgrades are only rarely reflected in the patches. Whenever a new patch is published (and sometimes oftener that that), I update my runtime files. You seem to be (like me) on a Unix-like system; what I use is (all on one line, and starting in the vim70 directory "for building", parent of src/ runtime/ etc.) rsync -avzcP --delete --exclude="/dos/" ftp.nluug.nl::Vim/runtime/ ./runtime/ 2>&1 | tee rsync.log Then (if I compile immediately afterwards) it will be installed as part of "make", or (if I don't compile) as part of "cd src && make installruntime". The above installs the latest versions from the Vim site. They are sometimes slightly out-of-date in relation to the versions on Dr. Chip's site, but not much, and this way I don't have to remove the versions from Dr. Chip's site from $VIM/vimfiles/... or $HOME/.vim/... once the versions from the official Vim site catch up with them. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 194. Your business cards contain your e-mail and home page address.
Re: What plugin is the one that does the following ...
On 4/23/07, Gary Johnson <[EMAIL PROTECTED]> wrote: On 2007-04-23, Andrew Falanga <[EMAIL PROTECTED]> wrote: > On 4/23/07, Taylor Venable <[EMAIL PROTECTED]> wrote: > > > > Do you mean the ability to "edit" a directory and read its contents? > > yes > > > > > > The documentation says that it's distributed with vim. However, I > > > installed vim using the FreeBSD ports system on my FreeBSD system and > > > this pluglin, apparently, isn't installed along with the rest of vim. > > > > That's odd. The FreeBSD ports build method for Vim is simply to > > download the patches, apply them, and do a standard build. To my > > knowledge, nothing is removed. One possibility I can think of: did you > > build a "LITE" version? (Using `make -DLITE install` for example.) > > > > What leads you to believe that this functionality isn't present? Do > > you get some sort of error messages when you try to do something? > > > > Every time I do something like, "gvim ." or "vim .", when vim loads on > the bottom of the screen I get ". is a directory" and there's nothing > in the window to actually "edit." > > I did do some searching on the install I did. I did not do a "-lite" > version in the ports tree. I did my install from > /usr/ports/editors/vim (there's a .../vim-lite in the same directory > of editors). I also found the netrw plugin referenced by Chip to > exist in /usr/local/share/vim/vim70/plugin. According to what I've > been able to determine, this should be sourced by vim when vim is > executed. However, try as I have to remember, I do not recall the > command to list the files vim sourced on startup. Can you provide > that for me? :scriptnames Make sure you have a _current_ version of the netrw plugin and that you have installed it according to Dr. Chip's instructions (earlier in this thread). Depending on the versions of the runtime files you originally installed, it may not be sufficient to download and install netrw.vba--you may also have to disable the current netrw files under the $VIMRUNTIME directory. I install vim on a variety of different machines and every now and then I forget to properly update netrw. When I do, the symptoms are as you describe. Regards, Gary Ok, thanks Gary. And thanks for the command. Andy
Re: What plugin is the one that does the following ...
On 2007-04-23, Andrew Falanga <[EMAIL PROTECTED]> wrote: > On 4/23/07, Taylor Venable <[EMAIL PROTECTED]> wrote: > > > > Do you mean the ability to "edit" a directory and read its contents? > > yes > > > > > > The documentation says that it's distributed with vim. However, I > > > installed vim using the FreeBSD ports system on my FreeBSD system and > > > this pluglin, apparently, isn't installed along with the rest of vim. > > > > That's odd. The FreeBSD ports build method for Vim is simply to > > download the patches, apply them, and do a standard build. To my > > knowledge, nothing is removed. One possibility I can think of: did you > > build a "LITE" version? (Using `make -DLITE install` for example.) > > > > What leads you to believe that this functionality isn't present? Do > > you get some sort of error messages when you try to do something? > > > > Every time I do something like, "gvim ." or "vim .", when vim loads on > the bottom of the screen I get ". is a directory" and there's nothing > in the window to actually "edit." > > I did do some searching on the install I did. I did not do a "-lite" > version in the ports tree. I did my install from > /usr/ports/editors/vim (there's a .../vim-lite in the same directory > of editors). I also found the netrw plugin referenced by Chip to > exist in /usr/local/share/vim/vim70/plugin. According to what I've > been able to determine, this should be sourced by vim when vim is > executed. However, try as I have to remember, I do not recall the > command to list the files vim sourced on startup. Can you provide > that for me? :scriptnames Make sure you have a _current_ version of the netrw plugin and that you have installed it according to Dr. Chip's instructions (earlier in this thread). Depending on the versions of the runtime files you originally installed, it may not be sufficient to download and install netrw.vba--you may also have to disable the current netrw files under the $VIMRUNTIME directory. I install vim on a variety of different machines and every now and then I forget to properly update netrw. When I do, the symptoms are as you describe. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: What plugin is the one that does the following ...
On 4/23/07, Taylor Venable <[EMAIL PROTECTED]> wrote: Do you mean the ability to "edit" a directory and read its contents? yes > The documentation says that it's distributed with vim. However, I > installed vim using the FreeBSD ports system on my FreeBSD system and > this pluglin, apparently, isn't installed along with the rest of vim. That's odd. The FreeBSD ports build method for Vim is simply to download the patches, apply them, and do a standard build. To my knowledge, nothing is removed. One possibility I can think of: did you build a "LITE" version? (Using `make -DLITE install` for example.) What leads you to believe that this functionality isn't present? Do you get some sort of error messages when you try to do something? Every time I do something like, "gvim ." or "vim .", when vim loads on the bottom of the screen I get ". is a directory" and there's nothing in the window to actually "edit." I did do some searching on the install I did. I did not do a "-lite" version in the ports tree. I did my install from /usr/ports/editors/vim (there's a .../vim-lite in the same directory of editors). I also found the netrw plugin referenced by Chip to exist in /usr/local/share/vim/vim70/plugin. According to what I've been able to determine, this should be sourced by vim when vim is executed. However, try as I have to remember, I do not recall the command to list the files vim sourced on startup. Can you provide that for me? Thanks for the help, Andy
Re: What plugin is the one that does the following ...
On Mon, 23 Apr 2007 09:27:18 -0600 "Andrew Falanga" <[EMAIL PROTECTED]> wrote: > I'm doing some reading on vim.org in the documentation areas and found > that the ability to browse a directory from within a buffer is > actually accomplished by plugins rather than being built into the vim > binary. I didn't know this. So, what plugin is it that accomplishes > what is referenced here > http://vimdoc.sourceforge.net/htmldoc/usr_22.html? Do you mean the ability to "edit" a directory and read its contents? > The documentation says that it's distributed with vim. However, I > installed vim using the FreeBSD ports system on my FreeBSD system and > this pluglin, apparently, isn't installed along with the rest of vim. That's odd. The FreeBSD ports build method for Vim is simply to download the patches, apply them, and do a standard build. To my knowledge, nothing is removed. One possibility I can think of: did you build a "LITE" version? (Using `make -DLITE install` for example.) What leads you to believe that this functionality isn't present? Do you get some sort of error messages when you try to do something? > While browsing for the plugin, I've found all sorts of plugins, but > the descriptions don't seem to match what this describes (or the > behavior I'm used to because I use the feature a lot in Linux). I'm > seeing minibufexplr.vim, bufexplorer.vim, SelectBuf.vim and a pluthra > of others, but the closest I've found yet is winmanager.vim. However, > like I said, it doesn't sound quite like what I'm looking for and I'm > hoping someone here knows the plugin I need. I actually use the Project plugin to do file navigation -- the downside (or I rather think of it as a benefit) is that you have to "register" what files you want it to list. Anyway, I think with a little more info, we may be able to further examine why the builtin version isn't working on your setup. -- Taylor Venable [EMAIL PROTECTED] http://www.metasyntax.net/
Re: What plugin is the one that does the following ...
Andrew Falanga wrote: I'm doing some reading on vim.org in the documentation areas and found that the ability to browse a directory from within a buffer is actually accomplished by plugins rather than being built into the vim binary. I didn't know this. So, what plugin is it that accomplishes what is referenced here http://vimdoc.sourceforge.net/htmldoc/usr_22.html? netrw.vim Its also been updated quite a bit since the original release of vim 7.0; so here's some directions on how to update it: To get an up-to-date version of netrw, you'll also need to get an up-to-date version of vimball. So: 1) Get up-to-date versions of vimball and netrw: vimball: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimBall (the mysite.verizon.net one will be the more recent version) netrw: http://vim.sourceforge.net/scripts/script.php?script_id=1075 -or- http://mysite.verizon.net/astronaut/vim/index.html#NETRW 2) Remove the old vimball plugin and install the new one: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/vimball*.vim autoload/vimball*.vim doc/pi_vimball.txt mv (wherever it was downloaded)/vimball.tar.gz . gunzip vimball.tar.gz tar -xvf vimball.tar Windows: Under Windows, check your runtimepath to determine where your vim 7.0's runtime directories are: vim :echo &rtp :q The first directory is likely your personal plugins directory, the second one is your vim system directory. cd (to your vim system directory) del plugin\vimballPlugin.vim del autoload\vimball.vim del doc\pi_vimball.txt ren (wherever)\vimball.tar.gz vimball.tar.gz gunzip vimball.tar.gz tar -xvf vimball.tar 3) Remove system version of netrw: Linux: cd /usr/local/share/vim/vim70 /bin/rm plugin/netrw*.vim autoload/netrw*.vim doc/pi_netrw.txt syntax/netrw*.vim Windows: cd (to your vim system directory) del plugin\netrwPlugin.vim del autoload\netrw.vim del doc\pi_netrw.txt del syntax\netrw.vim 4) Install an up-to-date version of netrw: vim netrw.vba.gz :so % :q Regards, Chip Campbell
What plugin is the one that does the following ...
Hi, I'm doing some reading on vim.org in the documentation areas and found that the ability to browse a directory from within a buffer is actually accomplished by plugins rather than being built into the vim binary. I didn't know this. So, what plugin is it that accomplishes what is referenced here http://vimdoc.sourceforge.net/htmldoc/usr_22.html? The documentation says that it's distributed with vim. However, I installed vim using the FreeBSD ports system on my FreeBSD system and this pluglin, apparently, isn't installed along with the rest of vim. While browsing for the plugin, I've found all sorts of plugins, but the descriptions don't seem to match what this describes (or the behavior I'm used to because I use the feature a lot in Linux). I'm seeing minibufexplr.vim, bufexplorer.vim, SelectBuf.vim and a pluthra of others, but the closest I've found yet is winmanager.vim. However, like I said, it doesn't sound quite like what I'm looking for and I'm hoping someone here knows the plugin I need. Thanks, Andy
