Re: [racket-users] Output Port Shenanigans

2018-03-14 Thread Ryan Culpepper
On 03/14/2018 06:16 PM, Lehi Toskin wrote: On Wednesday, March 14, 2018 at 10:10:20 AM UTC-7, Matthew Butterick wrote: probably it requires a combination of peek + read, or copying the port. That may be true, but I've been messing around getting *anything* to print from inside that

Re: [racket-users] Output Port Shenanigans

2018-03-14 Thread Lehi Toskin
On Wednesday, March 14, 2018 at 10:10:20 AM UTC-7, Matthew Butterick wrote: > > > probably it requires a combination of peek + read, or copying the port. > > That may be true, but I've been messing around getting *anything* to print from inside that function. I'm beginning to think it's never a

Re: [racket-users] Output Port Shenanigans

2018-03-14 Thread Matthew Butterick
> On Mar 13, 2018, at 8:50 AM, Lehi Toskin wrote: > > There must be something I'm missing, but there's not much in the docs that > would help me. Just a guess, but this kind of double-dipping on ports is usually not possible, because once bytes are read from a port, they're gone. If you want

[racket-users] Output Port Shenanigans

2018-03-13 Thread Lehi Toskin
Hello, everyone! I'm trying to get an output port to display text to both the error port and a text% object every time there's an error or an `eprintf` is called. Now, I have already accomplished this by using `make-output-port`, but I had decided to try and use `open-output-text-editor` instea