[1.11.1] Undefined method `chomp' for nil:NilClass about command-t HOT 12 CLOSED

Thanks for the report, @dymv. I'll see if I can figure out what's going on.
What version of Ruby is Command-T using, and have you overridden
any Command-T settings in your .vimrc?

On Friday, August 29, 2014, dymv [email protected] wrote:

After Command-T update I started getting the following error each time I
call :CommandT or use my mapping

[image: screenshot 2014-08-30 00 12 54]
https://cloud.githubusercontent.com/assets/755084/4095773/f1844ed6-2fb8-11e4-89f1-3a8005640118.png

—
Reply to this email directly or view it on GitHub
#109.

from command-t.

@wincent,

:ruby p RUBY_VERSION == "1.9.3"

I have these settings

let g:CommandTMaxFiles=240000
let g:CommandTMaxDepth=60
let g:CommandTWildIgnore=&wildignore . ",**/xcodebuild/*,**/out/*,*OWNERS,*.xtb"
let g:CommandTFileScanner="find"

But I've also tried without them (comment, so %, and flush).

Thank you!

from command-t.

Comment, sourcing and flushing won't have any effect, because:

• when Vim launched, you set g:CommandTSomething to "something", overriding the default and setting a global variable
• when you re-sourced the file, there were no let statements, so the override remained exactly as it was (the global is still in memory)
• you flush, and Command-T sees nothing new

You'd need to actually restart Vim to go back to the default Values, or override explicitly back to the default values:

:let g:CommandTWildIgnore=&wildignore
:let g:CommandTFileScanner="ruby"

from command-t.

Same issue here, vim and command-T compiled with OSX 10.9 system ruby (2.0.0-p451)
Only overridden settings in vimrc:

let g:CommandTMaxFiles=20000
let g:CommandTWildIgnore=&wildignore

Strangely enough, command-t works fine in it's own directory under .vim: ~/.vim/bundle/Command-T/if called anywhere beyond here

To note, I'm using Vundle for vim plugin packaging, no issues with other plugins though.

from command-t.

Commit 712fc17 seems to cause the issue for me. I reverted just that change and now no problems. Not sure if it's an issue with my environment but thought I'd give you a heads up.

Thanks for the amazing plugin.

from command-t.

I confirm reverting 712fc17 eliminates this error.

from command-t.

I don't know if this helps, but I was seeing this error when I was not under a git repository, but when I was it was fine. Reverting fixed it for me as well though.

from command-t.

Thanks for digging in and finding that. I'm traveling right now so don't
have much access, but I'll see if I can grab half an hour to cut a new
release with a fix.

On Tuesday, September 2, 2014, Edward Anderson [email protected]
wrote:

I confirm reverting 712fc17
712fc17
eliminates this error.

—
Reply to this email directly or view it on GitHub
#109 (comment).

from command-t.

Fix is out on the "master"/"next" branches, and in the just-cut 1.11.2 release. Thanks once again for all your help.

from command-t.

Thanks for the quick fix!​

from command-t.

Thanks! :)

from command-t.

Thanks! 😃

from command-t.