From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: vim-8.0.1376-1: Possible bug with ruby extensions
Date: Tue, 06 Feb 2018 18:26:00 -0000 [thread overview]
Message-ID: <5b396739-d7e3-b770-baa7-43e8788756a1@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAKrHFwkLF9EpZP+zrw=WRv_QZb3aptn7Cce4o9xDv7-RYBkEdA@mail.gmail.com>
On 2018-02-06 09:37, Ameya Vikram Singh wrote:
> Maintainers of the ViM/GViM text editor.
> I am noticing that currently with the latest build of ViM
> editor(vim-8.0.1376-1),
> I am unable to use the command-t [1] plugin with this release.
> When invoking the functionality with the key combination: `\` + `t`
> I get the following error message on the ViM editor:
> command-t.vim requires Vim to be compiled with Ruby support
> For more information type: :help command-t
> When checking the vim feature from the bash terminal using:
> vim --version
> I do see in the output `+ruby/dyn`, which means that ruby support
> should be enabled.
> When checking for ruby compatibility with ViM using the following in
> command mode:
> :ruby puts RUBY_VERSION
> One gets the following error message:
> E448: Could not load library function rb_assoc_new
> E266: Sorry, this command is disabled, the Ruby library could not be loaded.
> Press ENTER or type command to continue
> I will try to rebuild the from the sources (vim-8.0.1376-1-src) and
> see if the error persists.
You need to install the ruby package to provide the dynamic library for support.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-02-06 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 16:37 Ameya Vikram Singh
2018-02-06 18:26 ` Brian Inglis [this message]
2018-02-09 2:51 ` Ameya Vikram Singh
2018-02-09 18:35 ` Yaakov Selkowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b396739-d7e3-b770-baa7-43e8788756a1@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).