You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/modules/ROOT/pages/usage/code_evaluation.adoc
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,23 @@ the source buffer.
59
59
60
60
NOTE: WIP
61
61
62
+
While the basic evaluation commands discussed earlier should be enough for
63
+
most people, CIDER features a ton of additional evaluation commands.
64
+
Some of them are so peculiar that one can easily label them "exotic".
65
+
This section will briefly go over some of them.
66
+
67
+
Broadly speaking the exotic evaluation commands can be grouped in the following
68
+
categories:
69
+
70
+
- commands that pretty-print the result (e.g. `cider-pprint-eval-last-sexp`)
71
+
- commands that insert the result in the current buffer (e.g. `cider-eval-last-sexp-and-replace`)
72
+
- commands that evaluate an expression in a different context (e.g. with user-supplied bindings)
73
+
- commands that are a variation of some basic commands (e.g. `cider-eval-list-at-point` and `cider-eval-sexp-at-point`)
74
+
75
+
Most of the exotic evaluation commands don't have "top-level" keybindings
76
+
and should be accessed via CIDER's evaluation commands keymap (`cider-eval-commands-map`), meaning that they share the standard prefix `C-c C-v`. On top of this - several
77
+
related commands that pretty-print their result are grouped under `C-c C-v C-f`.
78
+
62
79
== Evaluating Clojure Code in the Minibuffer
63
80
64
81
You can evaluate Clojure code in the minibuffer at almost any time
0 commit comments