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

Feature request: pp button in REPL #466

Closed
voj opened this issue Aug 22, 2014 · 8 comments
Closed

Feature request: pp button in REPL #466

voj opened this issue Aug 22, 2014 · 8 comments
Milestone

Comments

@voj
Copy link

voj commented Aug 22, 2014

I find myself typing (clojure.pprint/pp) several times a week. It would be awesome to have a button for that.

@cursive-ide
Copy link
Owner

It seems like what you really want is a Live Template, see #332.

@voj
Copy link
Author

voj commented Aug 22, 2014

I guess what I really want is a toggle for pretty printing return values on the REPL, but Live Templates would certainly be good enough 80% of the time.

(I hope this didn't come across as sarcastic. The toggle actually only occurred to me after your reply.)

@cursive-ide
Copy link
Owner

Yeah, I'm actually planning another change to syntax highlight and pretty print values in the REPL automatically. My plan was to allow it to happen automatically, or provide a button as you suggest to format the last output item for people with a lot of REPL output who don't want the performance overhead.

@voj
Copy link
Author

voj commented Aug 22, 2014

That'd be nice :-)

@bluesxman
Copy link

Yes, that'd be great!

@sveri
Copy link

sveri commented Aug 22, 2015

I'd also like this feature, pprinting a map relatively often.

@rutchkiwi
Copy link

+1

@cursive-ide cursive-ide added this to the 0.1.69 milestone Nov 4, 2015
@cursive-ide
Copy link
Owner

In the next build there is now an option (on by default) to automatically format values returned from the REPL. This should be very fast, even for large maps. There's an additional sub-option to split multi-line strings and align them if required.

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

No branches or pull requests

6 participants