I noticed curious cursor behaviour when evaluating Clojure code in the editor buffer, which happens irrespective of if cider-show-error-buffer is set to t or nil (except when t then q should be pressed to quit the error buffer) I open a Clojure .clj file from a project which has a namespace definition: 1. Calling a function that is not defined will jump the cursor to the opening bracket of the call expression, (foo) 2. Calling an evaluated function with incorrect number of arguments does not move the cursor 3. Evaluating a non-existent symbol blahblah jumps the cursor to the top of the namespace Is this the expected behaviour for Cider? I assumed that 1. and 2. would behave the same, the cursor jumping to the start of the calling expression (or not moving) Behaviour 3 feels quite strange, I dont know what value is provided by the cursor jumping away (I appreciate this situation would not happen very often though) Is there a way to customise the cursor movement on error? Or is it simply the way its been implemented? Thank you