You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1597: Non-compiled version for cross compatibility

Kind feature request
Product Command-T
When Created , updated
Status open
Reporter anonymous
Tags no tags

Description

Hi Wincent,

I want to say what an amazing piece of Command-T is. Best vim plugin I have found in a long time!

Something that would be great would be to bundle a pure ruby implementation of the ruby-c extension in Command-T (alongside the c-extension)

I keep my .vim files in git so I can use them on any computer I work on. I routinely use Mac, Linux and Windows.

On my windows computers I do not have a c compiler. It would be great to be able to use command-t without having to worry about setting up a build environment. Having an option to use a pure-ruby version of command-t, even if slow, would allow me to do this.

What do you think?

- Jonno

Comments

  1. Greg Hurrell

    Yeah, it's a good idea. I think I'd prefer to have the pure Ruby version activated by a setting in your .vimrc rather than doing a transparent fallback, because I wouldn't want users to fail at compiling the C extension, end up running the pure Ruby version without realizing it, and conclude that Command-T is a slow piece of crap... ;-)

    If you look at the development history in the Git repo for the project, you can see that I first developed the prototype in pure Ruby and only later ported the performance-critical bits to C. So, yes, it could be done. Will mark this ticket as open and try to get to it shortly.

    Speaking of Windows, not a Windows user myself but I did do some testing using:

    To get a suitable Ruby environment and build tools. It's documented in the docs if you want to give it a try.

  2. Greg Hurrell

    Status changed:

    • From: new
    • To: open
  3. anonymous

    Thanks for the quick response. That sounds great, an option for vimrc is what I had in mind.

    heh, I did not see it in the git repo, but I figured you would have started out with a pure ruby version.

    Thanks for those links. That might be worth installing on my primary windows dev VM. At the moment I use git to distribute my vim scripts to windows, but I am thinking of using dropbox to distribute it to windows.

  4. Greg Hurrell

    Yeah it was pretty much a three-step process.

    So we're basically talking about resurrecting the old match.rb and matcher.rb files, and requiring them if and only if requiring the C extension fails and the user has the appropriate option set in his/her .vimrc.

  5. Greg Hurrell

    Closed ticket #1659 as a duplicate of this one.

Add a comment

Comments are now closed for this issue.

Menu