File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed
doc/modules/ROOT/pages/debugging Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change 1
1
= Inspector
2
2
:experimental:
3
3
4
- The value inspector allows you inspect and navigate the structure of data. While you can use
4
+ The value inspector allows you to inspect and navigate the structure of data. While you can use
5
5
it for pretty much anything (e.g. primitive data types, var, ref types) it's most
6
6
useful when you're dealing with (deeply) nested collection-like data types (e.g. a vector of maps).
7
7
8
8
== Usage
9
9
10
10
Typing kbd:[C-c M-i] (`cider-inspect`) after some form in a source
11
- buffer or the REPL will show you the structure for the result of the
12
- form in a new buffer. You can also use kbd:[C-u C-c M-i] to inspect
11
+ buffer or the REPL will show you the structure of the form's result
12
+ in a new buffer. You can also use kbd:[C-u C-c M-i] to inspect
13
13
the result of the current top-level form and kbd:[C-u C-u C-c M-i] to
14
14
read an expression from the minibuffer and inspect its result.
15
15
16
16
Alternatively, after a regular eval command, you can inspect the last
17
- evaluated value using `cider-inspect-last-result`. When a inspector
17
+ evaluated value using `cider-inspect-last-result`. When an inspector
18
18
buffer is visible in the background, it is automatically updated with
19
19
the last result. This behavior can be controlled with the variable
20
20
`cider-auto-inspect-after-eval`.
You can’t perform that action at this time.
0 commit comments