Le 28/11/2015 22:38, James McCoy a écrit :
> On Sun, Nov 29, 2015 at 08:24:15AM +1100, Craig Small wrote:
>> I've been helping someone with a vim plugin called vim-command-t[1] and
>> we've both hit a snag. The problem is that when I used pbuilder it
>> linked the plugin to libruby 2.2 but my vim
On Sat, Nov 28, 2015 at 04:38:45PM -0500, James McCoy wrote:
> On Sun, Nov 29, 2015 at 08:24:15AM +1100, Craig Small wrote:
> > But when foo tries to load plugin baz, it fails. Is it a problem with
> > the plugin? Should it be using "ruby things" via the binary?
>
> No, it's just normal turbulence
Thanks James,
If it is "just me" then its an easy fix.
- Craig
On Sun, Nov 29, 2015 at 8:39 AM James McCoy wrote:
> On Sun, Nov 29, 2015 at 08:24:15AM +1100, Craig Small wrote:
> > I've been helping someone with a vim plugin called vim-command-t[1] and
> > we've both hit a snag. The proble
On Sun, Nov 29, 2015 at 08:24:15AM +1100, Craig Small wrote:
> I've been helping someone with a vim plugin called vim-command-t[1] and
> we've both hit a snag. The problem is that when I used pbuilder it
> linked the plugin to libruby 2.2 but my vim is linked to libruby2.1
Your vim is outdated, t
I've been helping someone with a vim plugin called vim-command-t[1] and
we've both hit a snag. The problem is that when I used pbuilder it
linked the plugin to libruby 2.2 but my vim is linked to libruby2.1
Now, the package has in its dependencies libruby2.2. libruby2.2 and
libruby2.1 are both in
5 matches
Mail list logo