-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
*print-length* and *print-level* have unexpected consequences with set-env! in the REPL #586
Comments
arsenerei
changed the title
*print-length* and *print-level* has unexpected consequences with set-env! in the REPL
Feb 10, 2017
*print-length*
and *print-level*
has unexpected consequences with set-env!
in the REPL
arsenerei
changed the title
*print-length* and *print-level* has unexpected consequences with set-env! in the REPL
*print-length* and *print-level* have unexpected consequences with set-env! in the REPL
Feb 10, 2017
From the doc for |
RadicalZephyr
added a commit
to RadicalZephyr/boot
that referenced
this issue
Feb 11, 2017
This should prevent user setting of these values for reasonable use in the REPL from preventing `set-env!` from failing the printable-readable round-trip test. Fixes boot-clj#586.
alandipert
pushed a commit
that referenced
this issue
Mar 3, 2017
This should prevent user setting of these values for reasonable use in the REPL from preventing `set-env!` from failing the printable-readable round-trip test. Fixes #586.
Thanks for the report, this is fixed in master 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for all the effort you've put into boot!
I was trying to follow this post and got a "Unmatched delimiter: ]" exception when calling
(set-env! :dependencies '[[cheshire "5.5.0"]])
.After some debugging, I discovered it was the
*print-length*
and*print-level*
settings in my profile.boot causing the issue.I'm not sure if this is intended behavior, but it certainly caught me by surprise.
There are similar exceptions with
*print-length*
The text was updated successfully, but these errors were encountered: