| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
|
|
| |
This new setting controls whether or not the test-report-buffer is auto-selected after running a test. Default is true. Set to nil to prevent the report buffer selection.
|
|
|
|
|
|
| |
Maps received via nREPL have string keys. The Emacs Lisp text property
functions expect all property keys to be symbols. Thus we must first intern any
non-symbol property keys prior to applying them as text properties.
|
| |
|
|
|
|
| |
defcustom
|
| |
|
| |
|
|
|
|
| |
See https://github.com/jlr/rainbow-delimiters/issues/33 for details.
|
|\
| |
| | |
[Fix #776, #773, #733] Rewrite bencode parser
|
| |
| |
| |
| |
| |
| |
| | |
- nREPL dicts are now plists and accessor api is given by `nrepl-dict-p`,
`nrepl-dict-get` and `nrepl-dict-put`.
- nested stack is used for decoded messages to avoid re-parsing of incomplete messages
- queues are used for raw strings from server and for decoded requests
|
|/
|
|
|
|
|
| |
Pass the `cider-stacktrace-print-level` defcustom added in 2142ee5 when viewing
stacktraces for test errors.
Also, change `if` to a `when` to clarify intent.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This PR doesn't show the *cider-test-report* on successful tests anymore. Most
people will close that buffer anyway right after it popped up, and a message in
the echo area is probably enough to indicate that everything is fine. Setting
`cider-test-report-on-success` to `t` restores the old behaviour.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When running tests with cider-test failing tests are highlighted in the source
files, or if tests are passing again previous highlights are cleared. The code
that does this is using the `cider-find-var` function to find the buffer for a
vars under test and then does it's job.
`cider-find-var` used to move point to the line at which the var was found. This
is a problematic side effect, because code using `cider-find-var` to find the
buffer can't use save-excursion because it doesn't know which buffer to safe
beforehand.
This PR removes the `goto-line` in `cider-find-var` and returns just the buffer
without any side effect. The `cider-company-location` uses similar code as
`cider-find-var` but with `save-excursion` wrapped around it.
|
| |
|
|
|
|
| |
This is the same change as #666 repeated in another minor mode.
|
|
|
|
|
|
|
|
|
|
|
| |
The functions for resolving and jumping to vars and files had become
unwieldy. This makes them tractable, and uses the simplified behavior to fix:
1. The `cider-jump` and `cider-test-clear-highlights` cases where a var exists
after the file in which it was defined has been deleted.
2. The `cider-test-clear-highlights` case where the user closes one REPL session
and starts another in a different project.
|
|
|
|
| |
Also, add `cider-test-report-buffer` to `cider-ancilliary-buffers`.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previously this command was only enabled in the report buffer and on
tests that had previous failures/errors.
This requires `clojure-mode`
[#238](https://github.com/clojure-emacs/clojure-mode/pull/238).
Also, update context menus and key binding documentation.
|
|
Add 'cider-test' to replace the venerable, now-retired 'clojure-test-mode'.
|