Use *cider-read-eval* buffer for cider-read-and-eval error locations

[vspinu]

• On errors in cider-read-and-eval don't jump to non-existent locations but create a buffer with relevant ns-form and evaled expression
• Truly use cider-minibuffer-history in cider-read-from-minibuffer

[bbatsov]

As this command is generally used to eval only one-liners, I don't quite the get point of the proposed change.

[vspinu]

The point is twofold. First, rely on common cider-interactive-eval so that you don't have to maintain two different paradigms of evaluation. Second, if there is an error you are placed in a buffer with the code which you can modify and evaluate directly from that buffer, one-liner or not, it's more convenient to look and modify errors in a buffer than in the minibuffer.

The problem is that cider-eval-and-read must be changed to avoid jumping to non-existent error location in the current buffer. So, the alternative to the above is to use cider-eval as it was before.