I think it is a bad idea to dump output into the interactions that isn't being printed by the program.
There is a logging window, perhaps that can be used? Robby On Sun, Oct 29, 2017 at 5:25 PM, 'John Clements' via Racket Users <[email protected]> wrote: > This is a great idea: I feel like this change would deliver 80% of what I > want, and be easy to implement. It would give a concrete and recognizable > visual “path” of the compilation. I would not be inclined to delete it when > finished. Could it ever be long? Would it make other people unhappy to see > this output (presumably not in teaching languages?)? > > John > >> On Oct 28, 2017, at 13:42, Ben Greenman <[email protected]> wrote: >> >> I like the output `raco make -v ....` gives on the command-line. >> >> How about piping that into the interactions window? > > > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
