After more research, it seems that you will get these errors if you
try to autocomplete on a foreign fixture that does not exist
Another bug is that you also get the following error when accidentally
pressing on autocomplete in the middle of defining a column:
"/Users/demo/Library/Application Support/TextMate/Bundles/Ruby on
Rails.tmbundle/Support/lib/rails/inflector.rb:109:in /bin/bash: -c:
line 0: unexpected EOF while looking for matching `''
/bin/bash: -c: line 1: syntax error: unexpected end of fileempty?' for
nil:NilClass (NoMethodError)
from /Users/demo/Library/Application Support/TextMate/Bundles/Ruby
on Rails.tmbundle/Support/bin/fixture_auto_complete.rb:22:in "
While these aren't terrible bugs, it would be nice to have a more
graceful way of handling the scenarios... maybe just ignore the
keyboard shortcut?