Re: [arch-general] vim 7.2.245-1
2009/9/21 Jozsef
Hi. Before upgrading to vim 7.2.245-1 I removed vi, gvim and vim with pacman -R then I installed only vim 7.2.245-1 and I see my scripts and plugins for autocompition, buffers on top of window... are not working anymore. Anybody had some similar experience? Is there any fix for this or I need to start from begining and to search for scripts/plugins again and to install them from scratch?
I have a similar problem. All the ~/.vim/plugins/ links are orphan. All points to vim-script somewhere in /usr but I haven't that path in my machine. Any idea? What package install that directory or something like that? Thanks
On Mon, 21 Sep 2009, Javier Ramos Hidalgo wrote:
2009/9/21 Jozsef
Hi. Before upgrading to vim 7.2.245-1 I removed vi, gvim and vim with pacman -R then I installed only vim 7.2.245-1 and I see my scripts and plugins for autocompition, buffers on top of window... are not working anymore. Anybody had some similar experience? Is there any fix for this or I need to start from begining and to search for scripts/plugins again and to install them from scratch?
I have a similar problem. All the ~/.vim/plugins/ links are orphan. All points to vim-script somewhere in /usr but I haven't that path in my machine.
Any idea? What package install that directory or something like that?
Thanks
There is a /usr/share/vim folder and inside of it /plugin, /vim72 and /vimfiles I tried to copy my files from ~/.vim to all of that places and nothing worked. Don't know what to try else. -- Best, Jozsef Kurucity | Web & Graphic Designer +971 50 6783113 | jozefk@gmx.com
On Mon, 21 Sep 2009, Jozsef wrote:
On Mon, 21 Sep 2009, Javier Ramos Hidalgo wrote:
2009/9/21 Jozsef
Hi. Before upgrading to vim 7.2.245-1 I removed vi, gvim and vim with pacman -R then I installed only vim 7.2.245-1 and I see my scripts and plugins for autocompition, buffers on top of window... are not working anymore. Anybody had some similar experience? Is there any fix for this or I need to start from begining and to search for scripts/plugins again and to install them from scratch?
I have a similar problem. All the ~/.vim/plugins/ links are orphan. All points to vim-script somewhere in /usr but I haven't that path in my machine.
Any idea? What package install that directory or something like that?
Thanks
There is a /usr/share/vim folder and inside of it /plugin, /vim72 and /vimfiles I tried to copy my files from ~/.vim to all of that places and nothing worked. Don't know what to try else.
This is working: set runtimepath=~/.vim,/usr/share/vim,/usr/share/vim/vim72 Add that line to your ~./vimrc Will work until next update I guess. After that we will see what we will do. -- Best, Jozsef Kurucity | Web & Graphic Designer +971 50 6783113 | jozefk@gmx.com
On Mon, 21 Sep 2009, Jozsef wrote:
On Mon, 21 Sep 2009, Jozsef wrote:
On Mon, 21 Sep 2009, Javier Ramos Hidalgo wrote:
2009/9/21 Jozsef
Hi. Before upgrading to vim 7.2.245-1 I removed vi, gvim and vim with pacman -R then I installed only vim 7.2.245-1 and I see my scripts and plugins for autocompition, buffers on top of window... are not working anymore. Anybody had some similar experience? Is there any fix for this or I need to start from begining and to search for scripts/plugins again and to install them from scratch?
I have a similar problem. All the ~/.vim/plugins/ links are orphan. All points to vim-script somewhere in /usr but I haven't that path in my machine.
Any idea? What package install that directory or something like that?
Thanks
There is a /usr/share/vim folder and inside of it /plugin, /vim72 and /vimfiles I tried to copy my files from ~/.vim to all of that places and nothing worked. Don't know what to try else.
This is working: set runtimepath=~/.vim,/usr/share/vim,/usr/share/vim/vim72
Add that line to your ~./vimrc
Will work until next update I guess. After that we will see what we will do.
Getting this message after exit from Vim: mkdir: cannot create directory `/usr/share/vim/doc': Permission denied It's just annoying. -- Best, Jozsef Kurucity | Web & Graphic Designer +971 50 6783113 | jozefk@gmx.com
There is a /usr/share/vim folder and inside of it /plugin, /vim72 and /vimfiles I tried to copy my files from ~/.vim to all of that places and nothing worked. Don't know what to try else.
We try to be more compliant with upstream vim: the out of the box path consists of /usr/share/vim/vimfiles/after and /usr/share/vim/vim72, where the vimfiles/after one is the more desireable to use because it does not contain version information. The plugins bundled with Archlinux now use /usr/share/vim/vimfiles/after and they have been recompiled for that. The whole point of that was, that we never ever have to set the runtimepath again. HTH, -Tobias
On Mon, Sep 21, 2009 at 3:45 PM, Tobias Kieslich
There is a /usr/share/vim folder and inside of it /plugin, /vim72 and /vimfiles I tried to copy my files from ~/.vim to all of that places and nothing worked. Don't know what to try else.
We try to be more compliant with upstream vim: the out of the box path consists of /usr/share/vim/vimfiles/after and /usr/share/vim/vim72, where the vimfiles/after one is the more desireable to use because it does not contain version information.
The plugins bundled with Archlinux now use /usr/share/vim/vimfiles/after and they have been recompiled for that. The whole point of that was, that we never ever have to set the runtimepath again.
Hrrm, I don't know if we should be using the 'after' dir for default plugins installed by pacman. It seem like these actually belong in /usr/share/vim/vimfiles/plugin/. The after directory has a special purpose, and none of the plugins I can think of seem to fit that purpose. At least, it doesn't seem valid to use the after dir as a general rule.
On Mon, 21 Sep 2009, Aaron Griffin wrote:
Hrrm, I don't know if we should be using the 'after' dir for default plugins installed by pacman. It seem like these actually belong in /usr/share/vim/vimfiles/plugin/. The after directory has a special purpose, and none of the plugins I can think of seem to fit that purpose. At least, it doesn't seem valid to use the after dir as a general rule.
That might actually be the case, that we put them into plugin instead of after. And AFAIR that works out of the box as well. -T
On Mon, 21 Sep 2009, Tobias Kieslich wrote:
On Mon, 21 Sep 2009, Aaron Griffin wrote:
Hrrm, I don't know if we should be using the 'after' dir for default plugins installed by pacman. It seem like these actually belong in /usr/share/vim/vimfiles/plugin/. The after directory has a special purpose, and none of the plugins I can think of seem to fit that purpose. At least, it doesn't seem valid to use the after dir as a general rule.
That might actually be the case, that we put them into plugin instead of after. And AFAIR that works out of the box as well.
-T
I never used runtimepath before and everything worked fine. And I don't have a "after" directory in /usr/share/vim/vimfiles/ at the moment. Is it something I should create by myself? At least I'm happy my vim is working the same as before. Hope there will be always some kind of workaround for this issue. Or at least some tutorial/manual how to fix things once and for always. -- Best, Jozsef Kurucity | Web & Graphic Designer +971 50 6783113 | jozefk@gmx.com
On Tue, 22 Sep 2009, Jozsef wrote:
On Mon, 21 Sep 2009, Tobias Kieslich wrote:
On Mon, 21 Sep 2009, Aaron Griffin wrote:
Hrrm, I don't know if we should be using the 'after' dir for default plugins installed by pacman. It seem like these actually belong in /usr/share/vim/vimfiles/plugin/. The after directory has a special purpose, and none of the plugins I can think of seem to fit that purpose. At least, it doesn't seem valid to use the after dir as a general rule.
That might actually be the case, that we put them into plugin instead of after. And AFAIR that works out of the box as well.
-T
I never used runtimepath before and everything worked fine.
And I don't have a "after" directory in /usr/share/vim/vimfiles/ at the moment. Is it something I should create by myself?
At least I'm happy my vim is working the same as before. Hope there will be always some kind of workaround for this issue. Or at least some tutorial/manual how to fix things once and for always.
And all of that directories inside of /usr/share/vim/ are owned by root. It could be a reason why the plugins don't work if I copy them to vimfiles/plugins or vimfiles/after I'm not running vim as root, why should I do that? -- Best, Jozsef Kurucity | Web & Graphic Designer +971 50 6783113 | jozefk@gmx.com
participants (4)
-
Aaron Griffin
-
Javier Ramos Hidalgo
-
Jozsef
-
Tobias Kieslich