Sung Pae

I agree; this is actually on a todo list in the autoload script. I'll take a look tonight as I finish up #10. Thanks!

Hello, thanks for the feedback! I'm afraid I might need some clarification on these commands: ``` paredit-forward-down paredit-forward-up paredit-backward-down paredit-backward-up ``` Do these work differently from the following mappings? https://github.com/guns/vim-sexp/blob/b0878de275c343819377755ba4ea7ec112b94d4f/doc/vim-sexp.txt#L143-L174...

Howdy all! vim-sexp is not abandoned, but its maintainer is a little busy! For now, compound and element text objects work well, and moving sexps around still feels awesome. We...

@hugoduncan Yes! It's on the [todo list](https://github.com/technomancy/slamhound/blob/master/todo.org#static-analysis), but I've been waiting for a stable release. Do you think it's ready?

Ah, that's interesting; I never considered the combination of auto-qualifying keywords and aliases. I'll take a look later today. Thanks for the report!

Hello, I finally had a chance to look at this today. This `Invalid token` error occurs at read-time and therefore never reaches Slamhound's ns regrow loop. It is possible to...

It doesn't _require_ a new phase, but it avoids making `asplode` depend on `regrow`. I also think it's nicer if `asplode` returns a file's ns form without any interpretation. Anyway,...

Hi @devth. Yes, the syntax keywords are generated through reflection. I'll update them soon. Thanks for the reminder!

Hi oskarv! > In this case, the some-func part of the name some-func' becomes clojureFunc while the ' becomes clojureQuote, resulting in a name with two colors in it, which...

Thanks Neil, this sounds awfully familiar; I must have broken your fix to this very same problem when refactoring for the new syntax_keyword variables. Using `syntax match` for just the...