On Thu, May 25, 2006 at 02:38:30PM -0400, William O'Higgins Witteman wrote: > On Thu, May 25, 2006 at 01:26:12PM -0400, James Vega wrote: > >On Thu, May 25, 2006 at 12:02:35PM -0400, William O'Higgins Witteman wrote: > >> I'm hoping someone has a quick fix for this. I have installed vim-perl > >> on Debian (from unstable) > > > >Are you sure you're running vim.perl and not another one of the variants > >we provide? Try explicitly invoking vim.perl instead of vim. If that > >works, then there's probably another variant of Vim installed which is > >being pointed to by the alternatives system. You can see what > >alternatives are providing the vim binary via: > > Aha! You have spotted the problem. I have both vim-perl and vim-python > installed, and even though they have the same priority, the system is > defaulting to vim.python.
You can change that with update-alternatives --config, but then you'll run into a similar situation if you (or someone else on that machine) want to use Python to script Vim. :) > So now the question is, is it possible to enable both Perl and Python at > the same time? We have vim-full which has support for all the interpreters (minus MzScheme). This is one of the situations where binary distributions are lacking because there's a trade-off between trying to meet everyone's needs and having numerous different versions of the same program. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
