Re: Vim: Not able to activate plugins , ... missing vim folders? etc

Thanks Chip.

Signature:
"Bad company corrupts good character". -anonymous writer

".... Beautiful quotes ....". -Dalai Lama, http://thinkexist.com/quotes/dalai_lama/

Live Long And Prosper,

FriendOfFatBeagle

On Thu, May 28, 2015 at 9:12 AM, Charles Campbell <Charles.E.Campbell@nasa.gov> wrote:

FriendOfFatBeagle wrote:
>
> I am learning Vim .... on Linux Mint Cinnamom Rebecca (17.1), 64 bits
>
> I am learning plugins for Vim from here: http://www.swaroopch.com/notes/vim/
> There is a free download book.
>
> Excerpts from page 60 of book (http://files.swaroopch.com/vim/byte_of_vim_v051.pdf):
> " 2. To install your own plugins or plugins that you have download from somewhere, you can use your own plugin directory:
> • $HOME/.vim/plugin/ on Linux/BSD/Mac OS X
> … "
>
> The Vim help files also mentioned this via vim command, :help plugin
> USING A GLOBAL PLUGIN
>
> First read the text in the plugin itself to check for any special conditions.
> Then copy the file to your plugin directory:
>
> system plugin directory ~
> Unix ~/.vim/plugin/
>
>
> My $HOME is :
> ~ $ echo $HOME
> /home/foffb
>
> But there is no $HOME/.vim folder, even after I enable "Show hidden files".
> The vim folder I found is here, and plugin folder also shown is like so:
> /usr/share/vim/addons/plugin
>
> So I downloaded highlight_current_line.vim (found here http://www.vim.org/scripts/script.php?script_id=1652)
> as suggested in the book, and put it in the only Vim plugin folder I found:
>
> /usr/share/vim/addons/plugin/highlight_current_line.vim
>
> When I ran vim, and I moved cursor over a line of texts, the line is not highlighted !
> Meaning plugin, "highlight_current_line.vim", does not work.
>
> Questions … too many, but here are a few for now:
>
> 1) Why do I not a have same folder structure for Vim
> as mention in the Vim's help docs and the "A Byte of Vim" book?
> Meaning there is no .vim under $HOME folder.
> AND ....
> This is all the vim stuff I have under $HOME :
> ~ $ locate $HOME/.vim/plugin
>     No returned result ....
> ~ $ locate $HOME/.vim
> /home/foffb/.viminfo
>
> 2) Where should I put the plugin?
> Where does your .vim folder reside in your Linux?
>
> 3) What else did I missed?
>

1: that's not automatic; you need to   mkdir $HOME/.vim  yourself
2: depends on how your plugin is delivered.  A vimball will set itself
up, pretty much, for example, with a simple  vim plugin.vmb  and :so %.
If its not a vimball, perhaps the plugin comes with directions.
Tarballs need you to be in some directory (often $HOME/.vim) before
un-tarring.  The other distribution methods (vundle, etc) really need
you to install the associated plugin first --  but I'm sure that they
come with directions, so at least read their installation directions.
3: what kind of vim do you have?  try  using   :version   to see.   In
particular, you don't want a "Tiny" version if you're intending to use
plugins.  I myself use 7.4 with patches 1-725, Huge (for the nonce).

Regards,
Chip Campbell

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to a topic in the Google Groups "vim_use" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_use/8xgv2Z0yEw0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.