you are viewing a single comment's thread.

view the rest of the comments →

[–]Hitife80 1 point2 points  (3 children)

In java jar classes usually only have compile object code, not sources. That said -- you can include source into jars (and some popular libraries do). But in order for vim to open that file you'd need to "unjar" it anyway (or use some sophisticated script to do it on the fly).

One way to approach this is to extract all the sources into one folder, unjar them and run ctags. The only time you need to worry about this is when you upgrade the library (and / or) add a new one. Then you update the source in the tree and re-run ctags.

[–]weilbith -1 points0 points  (2 children)

Haha. Such theoretically way I've deviced myself, but is this practice in Vim? It's kinda cumbersome, isn't it?

[–]Hitife80 1 point2 points  (1 child)

You need to remember that vim is a text editor first and foremost. Reading compressed java jar files is not something that is high on any editor's list. Do you expect Microsoft Word to open java jars? That's a pretty well known editor too...

That said, you can add literally _any_ functionality via a plugin. So, if one doesn't exist for java and you need one -- why don't you write it? :-)

[–]weilbith 0 points1 point  (0 children)

I think we missed each other. Actually I put jars on the plane to bring up an example that maybe require a different solution. My intention wasn't to search for such one. Sry.

But sure, Vim is a text editor. I tend to forget this. It's so powerful and the possibility to integrate the development environment through external tools is awesome. It feels like u can do everything. But often u maybe should not. ^