How to create a .vim directory instead of .vimrc

English Applications
1

I was trying to install vim today and could not find .vim directory where I could install them and only the .vimrc file was there

So what I did was
Try making a .vim directory copy the .vimrc file in it and and removing the old ~/.vimrc file. I exported the ~/.vim/ to $VIMHOME

but nothing happened…
What do I do so as to have my configurations

2

i could be wrong, but i believe vim is installed by default, and i
wonder why yours was not…so, what version of what operating system
are you running?

and, why do want to have a .vim directory when (i think)
/home/[you]/.vimrc file is the correct name and placement for the vim
configurations for [you]

wait a moment, are both talking about the command line interface vim?
what version of vim did you install?

–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]

3

Yes… its installed by default I am sorry I misframed it
I have vim 7.2
Yes I am speaking about command line interface vim, but I suppose that can work on gvim to

I would like to install plugins on a per user basis so it would be good to have .vim at ~/.vim so that every user gets his own configuration instead of the common set

4

manugupt1 wrote:
> I would like to install plugins on a per user basis so it would be good
> to have .vim at ~/.vim so that every user gets his own configuration
> instead of the common set

maybe i don’t see the problem, because i think if each individual user
has their plugin installed to their /home (which i think is how it
should be) then every user will have their own configuration in the
file (not directory) named /home/[them]/.vimrc (as it should be)…

again, maybe i don’t quite understand the problem…sorry…but, i
still don’t see why you want to move the file each user should have
(.vimrc) in their home, inside a new directory named .vim

i’ve not looked at the code but i guess the default compiled vim
expects to look to the user’s /home/[userID]/.vimrc file for that
users configuration…AND, therefore if you try put that file here:
/home/[userID]/.vim/.vimrc it will not be found, and as you discovered
already “nothing happened”

i’ve not explored it, but maybe there is a setting to change where vim
looks for a user’s config file…have you looked at “man vim” and/or
“man info”

sorry, if i’m confused about this…

well, this is an openSUSE forum and vim is a tiny (but important) part
of openSUSE, perhaps you specific vim question could be better
answered in a vim forum post <http://vim.1045645.n5.nabble.com/>

i will revisit this thread hoping someone will set me straight if i’m
confused (maybe that someone will be you?)

–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]

5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes… vim by default uses the user’s .vimrc file from the user’s home
directory, but from there you can tell vim to do things like use plugins
(learn something new every day). The vim help talks about this, as do a
few million articles found via Google. From within vim this seemed useful
(when in command mode):

:help initialization

Which returned the following data:

  1. Load the plugin scripts. load-plugins
    This does the same as the command: >
    :runtime! plugin/**/*.vim
    The result is that all directories in the ‘runtimepath’ option will be
    searched for the “plugin” sub-directory and all files ending in “.vim”
    will be sourced (in alphabetical order per directory), also in
    subdirectories.
    Loading plugins won’t be done when:
  • The ‘loadplugins’ option was reset in a vimrc file.
  • The |–noplugin| command line argument is used.
  • The “-u NONE” command line argument is used |-u|.
  • When Vim was compiled without the |+eval| feature.
    Note that using “-c ‘set noloadplugins’” doesn’t work, because the
    commands from the command line have not been executed yet. You can
    use “–cmd ‘set noloadplugins’” |–cmd|.

To find out more about runtimepath I guessed the following within vim:

:help runtimepath

which gave me the following:

‘runtimepath’ ‘rtp’ string (default:
Unix: “$HOME/.vim,
$VIM/vimfiles,
$VIMRUNTIME,
$VIM/vimfiles/after,
$HOME/.vim/after”

Anyway, I thought that was all pretty neat and is likely useful for the
OP’s situation.

Good luck.

On 11/13/2010 08:31 AM, DenverD wrote:
> manugupt1 wrote:
> > I would like to install plugins on a per user basis so it would be good
>> to have .vim at ~/.vim so that every user gets his own configuration
>> instead of the common set
>
> maybe i don’t see the problem, because i think if each individual user
> has their plugin installed to their /home (which i think is how it
> should be) then every user will have their own configuration in the
> file (not directory) named /home/[them]/.vimrc (as it should be)…
>
> again, maybe i don’t quite understand the problem…sorry…but, i
> still don’t see why you want to move the file each user should have
> (.vimrc) in their home, inside a new directory named .vim
>
> i’ve not looked at the code but i guess the default compiled vim
> expects to look to the user’s /home/[userID]/.vimrc file for that
> users configuration…AND, therefore if you try put that file here:
> /home/[userID]/.vim/.vimrc it will not be found, and as you discovered
> already “nothing happened”
>
> i’ve not explored it, but maybe there is a setting to change where vim
> looks for a user’s config file…have you looked at “man vim” and/or
> “man info”
>
> sorry, if i’m confused about this…
>
> well, this is an openSUSE forum and vim is a tiny (but important) part
> of openSUSE, perhaps you specific vim question could be better
> answered in a vim forum post <http://vim.1045645.n5.nabble.com/>
>
> i will revisit this thread hoping someone will set me straight if i’m
> confused (maybe that someone will be you?)
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJM3sB+AAoJEF+XTK08PnB5g5sP+wawcPPiY3CxpCeF09opD/my
62L23TiSCfNi06i+3REs/GWdAPtmHHvKXNyDJF4P0IgmrFObtdKP8qJLdcipNdRJ
VlWXdyv5RXbf5vCMcal5RCXmo3xZ4JMx9vbQLzXm5woz5V5UWNjoF8d/tIfFymQN
UDX4o98S8U1RsokJakE4YQn4qdh7vPoNzqqo7o9qZWqDH5z4EBKlXZ5CmDek5ERz
G/aViuzQpErpzf8FrkOMwDdJxyuGuFx/ctT+LrlvXFo3gNzpJ8g8Nt1ZpHTCa2bk
+x3xTzUx9PajsfUw6OGdb/zkrHmh2I8inLb12wp/3Fph3xKkehTtJuhONSKinBfa
IApTU+WbfHyHjXgpWVx8vD5aRZ9Efg87kN+zNuHE68kVLuCTjclD/NHXCI8CN40I
CwytLadK5iRx10DaSNg8/C9E/UxINngR91XpueiuXQctPz95OdhJLEPWlTr3KKDe
JBfeDbWxOiy1d4d9XbPa+56dh3Cem+fjbtdwtJg5tSy3NB88byeCuGuqnaKaTsfB
SY+uMw0XRjQ8539JgJABmLSgSapWGSxbaIlj3I8yvfoy8ceFORYoS1+2r5iCEJdw
iIl5nqqSYkyTeNyJnQLJiEaM3eCufkhuh5iZvo+65sgK0LrA+gqaSLHmSeLwTaaM
dgSS6Va4TrYk3TBiUkne
=TLve
-----END PGP SIGNATURE-----

6

ab@novell.com wrote:
> The vim help talks about this, as do a few million articles found
> via Google.

teaching how to fish is a good thing…good on you!

–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]