≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Bug #1509

Bug #1509: "require" needs absolute path on Windows

Kind bug
Product Command-T
When 2010-03-23T03:19:02Z
Status closed
Reporter Greg Hurrell
Tags no tags

Description

From a user email:

I tried Command-T on WindowsXP with ruby1.87, and I make the "*.c" file successfully. but when I type <leader>t to call CommandShow(),It doesn't work.It tell me "No pwd method defined in VIM module"; I want to know ,can I use Command-T on Windows with gvim72?

And the solution:

I got it! I change the command-t.vim! change the "require vim" to absolute path "require E:\Vim\vimfiles\ruby\vim"

So the task now is to do some testing on Windows and figure out how to tweak the require statements so that they work without modification on both Windows and other platforms.

Comments

  1. Greg Hurrell 2010-03-23T06:53:34Z

    Ok, still can't test this on Windows seeing as I need to set up Parallels on this machine, but I think I might have addressed the issue.

    Instead of assuming a hard-coded location for the VIM runtime files (~/.vim) we consult the 'runtimepath' setting and try looking in the first entry in the list.

    I might even go so far as to walk through the list and try each location in turn.

  2. Greg Hurrell 2010-03-23T07:07:16Z

    Ok, just did that. Now we add all of the paths from the 'runtime' to the Ruby LOAD_PATH (at least, all of the paths which actually exist on the filesystem and have a ruby subdirectory in them).

    This should hopefully fix the bug for pretty much all possible install locations on all platforms.

    Will still do some testing though once I can on Windows, so not going to mark as closed just yet.

  3. Greg Hurrell 2010-03-23T15:18:49Z

    Gah, I got Windows XP installed on Parallels, but I realized I'm completely out of depth when it comes to finding/building a version of VIM with Ruby support, or getting a compiler tool chain installed to build the C extension.

    So I'm going to have to mark this one as closed and hope for the best.

  4. Greg Hurrell 2010-03-23T15:18:55Z

    Status changed:

    • From: new
    • To: closed
  5. Greg Hurrell 2010-03-23T16:48:18Z

    The new release is out.

Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets