Bug #1512: uninitialized constant CommandT::Match

 Error detected while processing /home/archlucas/.vim/plugin/command-t.vim:
 line  151:
 NameError: uninitialized constant CommandT::Match

 autoload :Match,        'command-t/ext.so'
 autoload :Matcher,      'command-t/ext.so'

Comments

1. Greg Hurrell 2010-03-24T09:41:08Z

   Thanks for the report.

   I am guessing from the fact that your home directory is a subdirectory of /home/, your VIM runtime files are in ~/.vim/, and your extension compiled with an .so extension, that you probably compiled on some Linux or Linux-like system.

   I'm actually a little surprised that autoloading just ext on its own doesn't work, seeing it picks up the built extension fine on Mac OS X (where it is called ext.bundle).

   Will see if I can dynamically detect the extension at runtime and append it so that you don't need to hand-edit those lines like you did.

2. Greg Hurrell 2010-03-24T14:28:48Z

   Just did some local testing here and looks like it's not specific to Linux or anything. I can reproduce on Mac OS X as well with Ruby 1.9.1; seems like without the extension autoload doesn't work, even though require does.

3. Greg Hurrell 2010-03-24T15:36:00Z

   Ok, this should be fixed now.

   Rather than messing with autoload strings at runtime (trying to detect platform, dynamically modifying filename string etc) the simplest and most robust solution was to replace use of autoload with good old-fashioned require statements. This should work fine with all versions of Ruby.

   This will be included in the next release, so going to mark as closed.

4. Greg Hurrell 2010-03-24T15:36:06Z

   Status changed:

   • From: new
   • To: closed

Add a comment

Comments are now closed for this issue.