Nothing that fancy. Just trying to make ctags understand namespaces & namespace aliases. Vim/Ctags works fine for non-namspaced function references, like:
(parseLong "5") However, the following won't work: (ns demo (:require [mylib.parse :as parse])) (parse/parseLong "5") ; fail "parse/parseLong" tag not found (mylib.parse/parseLong "5") ; fail "mylib.parse/parseLong" tag not found The problem is that the entire namespace part of a reference (either aliased or nor) is not recognized by ctags. Since ctags does not know anything about clojure namespaces, it thinks the whole thing is the function name, not just the part after the "/" character. Alan On Thu, Sep 4, 2014 at 11:52 AM, Jason Felice <jason.m.fel...@gmail.com> wrote: > Is using tools.analyzer.jvm overkill? Do you want to capture > pre-macro-expansion, post-marco-expanion, both? > > > On Thu, Sep 4, 2014 at 2:41 PM, Alan Thompson <clooj...@gmail.com> wrote: > >> Hi, >> >> I've been using Clojure & Vim for a year now, with fireplace, etc. >> However, it seems that Exuberant Ctags is a bit crippled since I have not >> found a way to make it understand namespace aliases. In my current work it >> seems that nearly every function is in a separate namespace with a >> namespace alias. >> >> Unless there is already a tool (or a ~/.ctags regex) to do that, I was >> thinking about writing a lein plugin (in clojure) to decode namespace >> aliases in the (ns...) form and create a tags file from scratch. About a >> year ago (in a previous job), I had to write a similar tool (in Groovy) to >> create the tags file for PL/I code, so I'm familiar with the ctags file >> format. >> >> Any thoughts? >> >> Alan >> >> P.S. I have been experimenting with LightTable but GVim is still my >> day-to-day workhorse. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
