[racket-users] UTF-8 encoding error when opening files in DrRacket on Windows 10

I have two students who just installed DrRacket on Windows 10 and get this error when they try to open files: bytes->string/locale: string is not a well-formed UTF-8 encoding string: #"\340lU\1" Has anyone else encountered this? -- You received this message because you are subscribed to the

Re: [racket-users] UTF-8 encoding error when opening files in DrRacket on Windows 10

We have had one other report yes. It looks like something is going wrong with the open file dialog. It may be possible to open files by double clicking on them to sidestep the bug I am not sure. Sorry about this. Robby On Thu, Sep 17, 2020 at 6:29 AM breanndan@gmail.com <

Re: [racket-users] UTF-8 encoding error when opening files in DrRacket on Windows 10

Thanks Robby. We'll experiment with that. Any idea if it's just the current version fo DrRacket? We could have them try installing the previous version for the time being. On Thursday, 17 September 2020 at 14:45:06 UTC+2 Robby Findler wrote: > We have had one other report yes. It looks like

Re: [racket-users] UTF-8 encoding error when opening files in DrRacket on Windows 10

I know only that we didn't get the report with earlier versions. BTW, if one click on the dialog that has the error message, there should be a "copy" option that will let you get some potentially valuable debugging information. If it is easy to get a student who is having the problem to do that,

Re: [racket-users] [racket users] describe variant issue?

> On Sep 15, 2020, at 3:11 PM, Sam Tobin-Hochstadt wrote: > > This is a difference in behavior between Racket BC and Racket CS, and > not something in the describe library: > > [samth@homer:~/work/teaching/c211 (master) racket-7.8] racket > Welcome to Racket v7.8. >> (struct->vector 5) >

Re: [racket-users] [racket users] describe variant issue?

We may change Racket CS so that it produces the same results, but in general the results of `struct->vector` on values that are opaque is not something that should be relied on. The describe library is, I believe, unmaintained, and hasn't been updated in many years. Sam On Thu, Sep 17, 2020 at

Re: [racket-users] [racket users] describe variant issue?

A PR to improve `struct->vector` for CS would be welcome. There relevant code is here: https://github.com/racket/racket/blob/master/racket/src/cs/rumble/struct.ss#L1221 As you'll see, the synthesized name is currently whatever comes out of Chez Scheme's `inspect/object` interface. It could