> Semantic/CEDET is ridiculously complex and lacking in documentation So, sooo much this. And it's a real shame, because semantic is quite a usable tool once y

> Semantic/CEDET is ridiculously complex and lacking in documentation So, sooo much this. And it's a real shame, because semantic is quite a usable tool once you get to know it. One thing I really wanted to have was a semantic index, a database of semantic symbols inside a project. I wanted to be able to write "Form" and have it display all the class names containing "Form". Grepping (even ag) is just much too slow and building my own index was too much work. I then saw "semanticdb" module. A week, I'm not kidding, a week - instead of half an hour - later I finally managed to preload a custom tag database and to query it. And that was with Python code, which has Semantic parser already, which is well integrated into the rest of CEDET. Now I'm fighting with CoffeeScript/LiveScript support. They both expose their parsers - I can get their AST with one line of code. After another week I still don't have working Semantic plugin for them. When I last checked, the activity on a CEDET and Semantic mailgroup was almost non-existent. The home page for CEDET looks like it comes from last century and even info pages are not a big help. It's a friggin shame, because when Semantic works, it does work well.