Newbie Setup Advice

[Vee Mur]

Hi folks,

I am new to vim.I recently installed vim 7.4 on my pc running ubuntu mate,now i've been trying to install several plugins without any success at all.

According to all the instructions on the various git reps i have to configure my .vimrc.My question is which .vimrc file do i edit because in my home directory its missing?I could only locate it in 3 locations /usr/share/vim -> /usr/share/vim/vimfiles -> /etc/vim


Please Help

Thanks

[Niels Kobschaetzki]

Create a new .vimrc in your home-directory and maybe a .gvimrc for
specific settings for gvim ("graphical" vim that you don't use inside a
terminal).

And I highly recommend that you use a plugin-manager for installing
plug-ins. My favorite one is NeoBundle:
https://github.com/Shougo/neobundle.vim

But there are others like vundle:
https://github.com/VundleVim/Vundle.vim pathogen:
https://github.com/tpope/vim-pathogen

Niels

[Nikolay Aleksandrovich Pavlov]

Pathogen is not a plugin manager.

>
> Niels
>
>
> --
> --
> 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+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[romainla...@gmail.com]

> I am new to vim.I recently installed vim 7.4 on my pc running ubuntu mate,now i've been trying to install several plugins without any success at all.

1. As a new user, you have more important things to do than installing plugins. Learning Vim and how to customize it will get you a loooong way.

> My question is which .vimrc file do i edit because in my home directory its missing?

2. I've written a short document explaining the basics of customization: https://github.com/romainl/idiomatic-vimrc/blob/master/idiomatic-vimrc.vim

[Ben Fritz]

On Monday, February 22, 2016 at 11:58:54 PM UTC-6, ZyX wrote:
>
> Pathogen is not a plugin manager.
>

I understand this sentiment, especially coming from someone such as yourself who works on a very fully featured plugin manager with abilities such as enabling or disabling plugins at runtime or automatically updating installed plugins.

But...what should we call Pathogen? Granted, it doesn't really do any actual managing of plugins itself, but it enables you to do so much more easily.

Without Pathogen, it is difficult to track down all files associated with a plugin. Thus it is mildly difficult to install and quite difficult to uninstall. Using Pathogen each plugin gets its own directory which is a large improvement over the status quo (although that's changing I understand from recent patches to the Vim core).

Does that make Pathogen a "plugin management tool" rather than a "plugin manager?" I can't really think of a better term for a tool that helps you manage plugins yourself.

[Nikolay Aleksandrovich Pavlov]

It is neither “plugin management tool” nor “plugin manager”, these are
the same things. It is manipulating runtimepath and if you need a
separate word (rather useless because there is only one such tool)
that would be [runtime]path manager: it does not manages plugins in
any fashion, it only does something to the running Vim and the only
“external” action is generating helptags at request.

[Bram Moolenaar]

I haven't actually used Pathogen myself, but I think the new 'packpath'
feature replaces most of it.

Rewriting the example from Pathogen:

mkdir -p ~/.vim/pack/tpope/ever
cd !$
git clone git://github.com/tpope/vim-sensible.git

What would still be useful:
:Helptags update all doc/tags files

And perhaps:
:PackUpdate find all git/mercurial repositories under
'packpath' and update them.

These can be done with Vim script. Any volunteers?

--
There are three kinds of people: Those who can count & those who can't.

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

[Matthew Desjardins]

Can this actually replace Pathogen? It doesn't look like it deals with plugins without a "plugin" directory (so things like colors or ftplugins), does it?

[Vee Mur]

Hi

Thanks for the advice,i guess i'm trying to run before i could run.However i'm still in the dark because there's no .vim file either in my home directory

[sycc]

> Hi
>
> Thanks for the advice,i guess i'm trying to run before i could run.However i'm still in the dark because there's no .vim file either in my home directory

The .vim file in your home directory is actually a directory itself. If
it doesn't exist you can just go ahead and create it. This is where your
user will store plugins, syntax extensions, etc.
For the .vimrc file it's the same deal, this one is a regular file and
if it's not there just create it yourself.

[Vee Mur]

Okay thanks

[Vee Mur]

On Wednesday, February 24, 2016 at 12:12:41 AM UTC, sycc wrote:

Sorry to bug.Do i have to recreate the whole directory structure as found in
/usr/share/vim?

[sycc]

> Sorry to bug.Do i have to recreate the whole directory structure as found in
> /usr/share/vim?

Not at all. You don't even need to create the .vim directory if you
don't need it. If you do, then just create whatever you currently
require, you'll then go about filling it up with other stuff once you
have to.