Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A feature I miss from CIDER is that
cider-inspect-last-result
. ThisPR provides somewhat similar feature to that. CIDER has it's own very
powerful inspector but here I just used the
pp-display-expression
function from
pp.el
.When
eros-inspect-last-result
is called, it shows the result of lasteros-eval-last-sexp
in a pretty printed format in a different buffernamed
*eros-inspect*
. If the*eros-inspect*
buffer is alreadycreated, every call to
eros-eval-last-sexp
updates the contents ofthe
*eros-inspect*
buffer automatically.I don't know if you want to include something like this (or even if
you are maintaining the project actively still) but I was going to
implement it for myself and thought I could open a PR.