Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add eros-inspect-last-result #6

Merged
merged 3 commits into from Mar 9, 2023
Merged

Add eros-inspect-last-result #6

merged 3 commits into from Mar 9, 2023

Conversation

isamert
Copy link
Contributor

@isamert isamert commented Mar 13, 2022

A feature I miss from CIDER is that cider-inspect-last-result. This
PR 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 last
eros-eval-last-sexp in a pretty printed format in a different buffer
named *eros-inspect*. If the *eros-inspect* buffer is already
created, every call to eros-eval-last-sexp updates the contents of
the *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.

@xiongtx
Copy link
Owner

xiongtx commented Mar 9, 2023

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants