Wilfred Hughes
Wilfred Hughes
E.g. it would be nice to do: ```emacs-lisp ;; Inputs '((a . 1) (b . 2)) ;; Output '(a b) ;; Figure out (mapcar #'cons input-here) ```
This means that copying output elisp into other files means you can't edit the code there either!
Given the following code: ``` js var _ = require('lodash'); function foo() { var x = {a: 1, b:2, c: 2}; return _.mapValues(x, function(v) { return v + 1;}); }...
If a symbol is defined outside of core, we know that it's not used inside core.
For example: ``` (-let [foo (bar baz)]) ``` We don't currently see this as a call to `bar`. Ideally we would macro expand, or treat `-let` and `-let*` specially.
When there's a large number of results (e.g. searching for all references to `defadvice`), it becomes a little difficult to see what's what.
Going to the beginning of the file is slightly surprising, especially when there's only a single match in that file.
This would be a great way of finding references in docstrings.
Currently it only cycles between matches.