Latest vim upgrade screws up aqua variant?
Good day, since the vim port has been bumped to patchlevel 192, the aqua variant seems to have problems: E484: Can't open file /opt/local/Vim.app/Contents/Resources/vim/syntax/syntax.vim So it seems gvim looks for syntax highlighting definitions at the wrong place. Also the main menu does not have any entries except for the leftmost "vim". This happens under a recent OS X Tiger, Intel Mac. Building vim without aqua support however works fine. Has somebody else encountered this? Regards, Riggs
Hello, sudo ln -s /Applications/MacPorts/Vim/Vim.app/Contents/Resources/ vim/ /opt/local/Vim.app/Contents/Resources/vim should fix the problem. (this is a workaround, I'm working on a solution) On Feb 10, 2007, at 5:06 PM, Thomas Zander wrote:
Good day,
since the vim port has been bumped to patchlevel 192, the aqua variant seems to have problems: E484: Can't open file /opt/local/Vim.app/Contents/Resources/vim/syntax/syntax.vim
So it seems gvim looks for syntax highlighting definitions at the wrong place. Also the main menu does not have any entries except for the leftmost "vim". This happens under a recent OS X Tiger, Intel Mac.
Building vim without aqua support however works fine.
Has somebody else encountered this?
Regards, Riggs _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
This is a duplicate of #11315. https://svn.macosforge.org/projects/macports/ticket/11315 Regards, Elias On Feb 10, 2007, at 5:06 PM, Thomas Zander wrote:
Good day,
since the vim port has been bumped to patchlevel 192, the aqua variant seems to have problems: E484: Can't open file /opt/local/Vim.app/Contents/Resources/vim/syntax/syntax.vim
So it seems gvim looks for syntax highlighting definitions at the wrong place. Also the main menu does not have any entries except for the leftmost "vim". This happens under a recent OS X Tiger, Intel Mac.
Building vim without aqua support however works fine.
Has somebody else encountered this?
Regards, Riggs _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Hi, On 10/02/07, Elias Pipping <pipping@macports.org> wrote:
sudo ln -s /Applications/MacPorts/Vim/Vim.app/Contents/Resources/ vim/ /opt/local/Vim.app/Contents/Resources/vim
should fix the problem. (this is a workaround, I'm working on a solution)
okay, sounds good. So it is not a problem of my particular installation. Thanks in advance, Riggs
Hello, the problem should no longer exist: https://svn.macosforge.org/projects/macports/changeset/21868 (you might need to wait for the portindex to be updated - that means no longer than 12 hours) Regards, Elias On Feb 10, 2007, at 9:14 PM, Thomas Zander wrote:
Hi,
On 10/02/07, Elias Pipping <pipping@macports.org> wrote:
sudo ln -s /Applications/MacPorts/Vim/Vim.app/Contents/Resources/ vim/ /opt/local/Vim.app/Contents/Resources/vim
should fix the problem. (this is a workaround, I'm working on a solution)
okay, sounds good. So it is not a problem of my particular installation.
Thanks in advance, Riggs
Hi, On 10/02/07, Elias Pipping <pipping@macports.org> wrote:
the problem should no longer exist:
sorry, despite not upgrading but complete uninstall/install of the vim port (the _1 revision this time), it is still looking for the resources in the wrong place and I have to apply the symlink workaround manually. But it was a good idea to mention that the vim aqua port requires a complete deinstall / install procedure. When I crossed this in the first place it felt quite unexpected because the upgrading process usually works surprisingly fine with macports. Riggs
participants (2)
-
Elias Pipping
-
Thomas Zander