-
Notifications
You must be signed in to change notification settings - Fork 90
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
Incremental Output #67
Comments
Have you tried println?
…On Sat, 21 Apr 2018, 01:27 Ben Denham, ***@***.***> wrote:
Is there currently a way to incrementally update a cell's output? E.g. to
provide a progress bar for some long-running background thread?
The closest I've come so far is the following snippet, which immediately
prints "Let the above loop run in the background", but any calls to
display after the cell has finished its initial output seem to be
buffered until the next time the cell is executed:
(require '[clojupyter.misc.display :refer [display]])
(future
(doseq [i (range 10)]
(Thread/sleep (* i 100))
(display (str "Completed " i))))
(println "Let the above loop run in the background")
Also, thanks for the super useful kernel!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#67>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADjHTBsf2ciZQ5sUCNesux_hB8t1Tk96ks5tqn0IgaJpZM4TePVs>
.
|
It is indeed possible to incrementally update a cell, as in
which will print numbers 0-9 and finally return |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there currently a way to incrementally update a cell's output? E.g. to provide a progress bar for some long-running background thread?
The closest I've come so far is the following snippet, which immediately prints "Let the above loop run in the background", but any calls to
display
after the cell has finished its initial output seem to be buffered until the next time the cell is executed:Also, thanks for the super useful kernel!
The text was updated successfully, but these errors were encountered: