-
-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keybindings in Test Report Mode not working. #885
Comments
Yep, this is definitely a bug. Will investigate! |
A quick look at the issue shows that the problem's here https://github.com/clojure-emacs/cider/blob/master/cider-test.el#L158 The properties are all present, but aren't retrieved for some bizarre reason. Will investigate more when I can. Anyone is welcome to lend a hand in the meantime. |
Not sure what you mean by 'The properties are all present' because in a test report buffer when I evaluate Where should point be for this to work? |
Place your cursor over a test name and type |
ah! I see what you mean now. sorry for the misunderstanding and thank you for explaining. |
I'm seeing the same bug, and have a superficial diagnosis, but I can't figure out how the relevant code should be working to find what's missing. The problem is that the properties on the text are named by strings (e.g. "actual") instead of Emacs Lisp symbols (e.g. 'actual). The Emacs |
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. Fixes clojure-emacs#885.
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.
I first noticed this in 0.7.0 and have also seen it in 0.8.0 and just reconfirmed the problem in 0.8.1 (each run with matching nrepl version). Emacs version 24.4.50.1.
When a failing test causes the Test Report Mode window to open some keybindings are not working.
d
,e
&t
all seem to have no effect.It seems that no matter where point is when
e
is pressed the same message is shownNo test error at point
. Same withd
except that the message isNo test failure at point
.With
t
if point is not on a symbol it prompts for a symbol to jump to. When on a symbol it will jump to it but when point is on a useful symbol such as the test name then there is an error with messageSymbol <test-name> not resolved
.The text was updated successfully, but these errors were encountered: