Strange issue with Pathogen

[Some Developer]

I'm having a strange issue with Pathogen. I'm trying to keep my Vim
configuration and plugins organised as I need to use it on several
computers so I decided to create a git repo for it.

The following is my .vim folder structure:

autoload
bundle
vimrc_config

When I symlink ~/.vimrc to ~/.vim/vimrc_config Pathogen does not load
any plugins at all. When I copy ~/.vim/vimrc_config to ~/.vimrc on the
other hand it works perfectly.

It would be nice if I could fix this issue as that would make it nice
and easy to distribute the full config in the Git repo and I would only
need to maintain one copy of the file. Since I need to copy the file to
make it work if I want to make a change to the file I need to change
both which is highly annoying and is error prone.

Does anyone have any ideas at all?

[Ben Fritz]

I don't have any idea why this would fail. Your method should probably work.

A workaround (which I use, because I use Vim on Windows XP without an easy way to make sym links) is to instead create a VERY simple .vimrc that looks something like this:

source ~/.vim/vimrc_config

[Rostislav Svoboda]

> I'm having a strange issue with Pathogen. I'm trying to keep my Vim

> configuration and plugins organised on several computers

> so I decided to create a git repo for it.

I had the same problem and realized Vundle works for me better than pathogen

Bost

[Tony Mechelynck]

Symlinks are a relatively new feature on Windows (compared to Unix-like
OSes where it existed since antiquity) so maybe Vim for Windows doesn't
know how to follow symlinks, or to make sure that they are followed.

Ben's "source" approach is the most portable, and for Vim, that's a
great plus.

Hardlinks (which are totally transparent to the application) would work
too, but unlike symlinks (and the :source statement) they can't cross
filesystem (i.e. disk partition) boundaries.


Best regards,
Tony.
--
ARTHUR: Ni!
BEDEVERE: Nu!
ARTHUR: No. Ni! More like this. "Ni"!
BEDEVERE: Ni, ni, ni!
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD

[Phil Dobbin]

I second the suggestion to use Vundle.

I keep my vimrc in Github & then clone it to any machine I'm going to
use (after cloning Vundle, of course) & then run `:BundleInstall` &
there's my plugins.

I also keep my colors & syntax directories in Github & a couple of
plugins that don't really work via Vundle (i.e. toggle_width.vim for
NERDTree) & a very basic bashrc which adds full color to the terminal
for Powerline, etc.

I've used it on CentOS, Debian, Fedora, OS X & Ubuntu & they all work
but not Windows 'cause I don't use it so have never tried it, so I can't
comment.

If you want to see it, it's at
<http://github.com/horse-latitudes/horse-vimfiles>.

Cheers,

Phil...

--
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing

[Martin Braun]

On 10/31/2012 02:47 PM, Some Developer wrote:
> I'm having a strange issue with Pathogen. I'm trying to keep my Vim
> configuration and plugins organised as I need to use it on several
> computers so I decided to create a git repo for it.
>
> The following is my .vim folder structure:
>
> autoload
> bundle
> vimrc_config
>
> When I symlink ~/.vimrc to ~/.vim/vimrc_config Pathogen does not load
> any plugins at all. When I copy ~/.vim/vimrc_config to ~/.vimrc on the
> other hand it works perfectly.

This is exactly how I handle the vimrc/pathogen problem, and it works
fine for me.
Have you checked the permissions for vimrc?

M

[Alejandro Exojo]

El Miércoles, 31 de octubre de 2012, Some Developer escribió:
> It would be nice if I could fix this issue as that would make it nice
> and easy to distribute the full config in the Git repo and I would only
> need to maintain one copy of the file. Since I need to copy the file to
> make it work if I want to make a change to the file I need to change
> both which is highly annoying and is error prone.

Of course this is possible and is what many people already does:

http://vimcasts.org/e/27/

> Does anyone have any ideas at all?

I am doing what you say. Both my .vimrc and my .vim are symbolic links, and
everything works as expected. You must be doing something else wrong.

You don't mention what OS are you using, but the user agent of your mail
program says is Windows. Are you using Cygwin?

--
Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2
http://barnacity.net/ | http://disperso.net

[Some Developer]

On 02/11/2012 08:35, Alejandro Exojo wrote:
> El Mi�rcoles, 31 de octubre de 2012, Some Developer escribi�:

>> It would be nice if I could fix this issue as that would make it nice
>> and easy to distribute the full config in the Git repo and I would only
>> need to maintain one copy of the file. Since I need to copy the file to
>> make it work if I want to make a change to the file I need to change
>> both which is highly annoying and is error prone.
> Of course this is possible and is what many people already does:
>
> http://vimcasts.org/e/27/
>
>> Does anyone have any ideas at all?
> I am doing what you say. Both my .vimrc and my .vim are symbolic links, and
> everything works as expected. You must be doing something else wrong.
>
> You don't mention what OS are you using, but the user agent of your mail
> program says is Windows. Are you using Cygwin?
>

I'm using Lubuntu. Probably should have stated that in my original post.

I'll give you the steps I take to get to the stage above:

cd ~
rm -rf .vim*
rm .gvimrc
git clone <REPO_URL> .vim
cd .vim
git submodule init
git submodule update
ln -s ~/.vimrc ~/.vim/vimrc_config

pretty much all there is to it.

[Some Developer]

On 02/11/2012 19:18, Some Developer wrote:
> ln -s ~/.vimrc ~/.vim/vimrc_config

Whoops. Typo.

ln -s ~/.vim/vimrc_config ~/.vimrc

[Alejandro Exojo]

El Viernes, 2 de noviembre de 2012, Some Developer escribió:
> I'll give you the steps I take to get to the stage above:
>
> cd ~
> rm -rf .vim*
> rm .gvimrc
> git clone <REPO_URL> .vim
> cd .vim
> git submodule init
> git submodule update
> ln -s ~/.vimrc ~/.vim/vimrc_config
>
> pretty much all there is to it.

Are you calling pathogen#infect with the proper directory to initialize
everything?

If you want, give a look to how I am doing it:

https://github.com/suy/configs