Error with ruby 2.0.0p0

[mdi]

I'm getting this error when using gem-ctags with ruby v2.0.0p0:

ERROR:  While executing gem ... (Errno::EISDIR)
Is a directory - tags

[tpope]

It's probably an issue with a specific gem rather than 2.0 per se. Is there enough context to show you what gem it's trying to index?

[mdi]

No that's all the context I can see.

[deiga]

Can you list the gems you have installed?
Do you use rvm or rbenv-bundle, so you might be able to make empty gemsets and figure out which gem is doing this?

[mdi]

Here's a list. And no, I'm just using rbenv. No gemsets or anything.

[deiga]

Okay, I'm installing these in a gemset to see if I can reproduce this. Can you tell me what you were doing when the error came up?
I presume your using the newest version of everything, since you didn't specify versions?

[deiga]

This issue is generated by backports 3.1.1, if gem-ctags has somekind of options file to exclude gems you could resolve this that way. Or stop using backports gem or wait until someone fixes gem-ctags to work with it

[deiga]

Basically this issue is because gem-ctags checks for available "tabs" file, which happens to be a directory in backports(

[mdi]

Ah okay. Thanks! backports was installed as a dependency to another gem I'm using, so I guess I'm just stuck with it for now. And all I was doing when this error occurred was running gem ctags to make sure it was up-to-date.

[tpope]

I just pushed a change to make things a bit less fatal. Try out the latest version in Git and let me know what you think.

rake build
gem install pkg/gem-ctags*.gem

[mdi]

Definitely better debugging output. Here's what I got when I ran it this time:

Generating ctags for backports-3.1.1
ctags: Failure on attempt to read file : Is a directory

[lzap]

Fiy this has nothing to do with Ruby 2.0. It is a different issue which has been partially fixed in master now and I have provided a final fix: #6

[mdi]

Yes, @deiga figured out it was an issue with the backports gem. I only noticed it when I upgraded to ruby v2, so I (wrongly) assumed it was a ruby v2 issue.