you probably want to use set! for that instead of alter-var-root.
On Wed, May 21, 2014 at 5:44 PM, Gary Trakhman wrote:
> Ah, so in my case, I run that snippet when I want *other* threads to write
> to stdout/stderr buffers instead of showing up in the terminal. In your
> case, you could rebind
Ah, so in my case, I run that snippet when I want *other* threads to write
to stdout/stderr buffers instead of showing up in the terminal. In your
case, you could rebind vim's *err* to its *out*, since you say anything
sent to *err* doesn't show up (unless it's not seeing vim's binding), but
*out*
On Wednesday, May 21, 2014 2:10:06 PM UTC-7, Gary Trakhman wrote:
>
> I use this trick pretty much all the time.
>
> (alter-var-root #'*out* (constantly *out*)), same for *err*, though I'll
> wire *err* to *out*
>
>
Wow, I have no clue what that does. When do you run this? When would *out*
not
I use this trick pretty much all the time.
(alter-var-root #'*out* (constantly *out*)), same for *err*, though I'll
wire *err* to *out*
(future (println "blah3")) works because *out* is conveyed to the future
via binding-conveyor-function.
That's not the case in the first.
On Wed, May 21, 201
A small clue, gleaned from a cider issue:
This outputs to the repl terminal.
(future (.start (Thread. #(println "blah2"
This output is captured by vim.
(future (println "blah3"))
Still no idea what's going on.
On Wednesday, May 21, 2014 1:09:31 PM UTC-7, Brian Craft wrote:
>
> Still not a
