bug#22901: drain-input doesn't decode

2021-05-19 Thread Taylan Kammer
Closing this since it's 5 years old and fixed in Guile 2.1 and higher. -- Taylan

bug#22901: drain-input doesn't decode

2021-05-16 Thread Taylan Kammer
Are we still maintaining 2.0, or can this issue be closed? -- Taylan

bug#22901: drain-input doesn't decode

2017-02-26 Thread Matt Wette
> On Feb 26, 2017, at 9:46 AM, Matt Wette wrote: > > I put together a test and tried on 2.1.7 - my test fails. See attached. > > (pass-if "encoded input" >(let ((fn (test-file)) > (nc "utf-8") > (st "\u03b2\u03b1\u03b4 \u03b1\u03c3\u03c3 am I.") > ;;(st "hello, wor

bug#22901: drain-input doesn't decode

2017-02-26 Thread Matt Wette
I put together a test and tried on 2.1.7 - my test fails. See attached. (pass-if "encoded input" (let ((fn (test-file)) (nc "utf-8") (st "\u03b2\u03b1\u03b4 \u03b1\u03c3\u03c3 am I.") ;;(st "hello, world\n") ) (let ((p1 (open-output-file fn #:en

bug#22901: drain-input doesn't decode

2016-06-20 Thread Andy Wingo
On Fri 04 Mar 2016 04:09, Zefram writes: > The documentation for drain-input says that it returns a string of > characters, implying that the result is equivalent to what you'd get > from calling read-char some number of times. In fact it differs in a > significant respect: whereas read-char dec

bug#22901: drain-input doesn't decode

2016-03-03 Thread Zefram
The documentation for drain-input says that it returns a string of characters, implying that the result is equivalent to what you'd get from calling read-char some number of times. In fact it differs in a significant respect: whereas read-char decodes input octets according to the port's selected