00:11 (quit) rbarraud: Ping timeout: 252 seconds
00:38 (join) reified
00:38 (quit) reified: Client Quit
00:43 (join) rbarraud
00:49 (quit) Fare: Ping timeout: 272 seconds
01:01 (join) Fare
02:19 Lajla: chandler, but you reckon that you can write a racket implementation in racket?
02:27 (quit) adadglgmut: Max SendQ exceeded
02:29 (join) adadglgmut
02:54 (quit) jonrafkind: Ping timeout: 252 seconds
03:00 neilv: i'm trying to skim this technical article while debugging, but the web site has run all the text through a pirate-speak filter
03:02 neilv: "The performance o' RSA is highly asymmetric, we'll keel-haul ye!"
03:02 neilv: someone should be shot
03:25 Lajla: neilv, I agree!
03:28 (nick) Lajla -> Allah-
03:28 (nick) Allah- -> Lajla-
03:29 (nick) Lajla- -> Lajla
03:50 (quit) flintf_: Quit: Lost terminal
04:12 (join) masm
04:22 (quit) neilv: Ping timeout: 240 seconds
04:59 (join) dzhus
05:02 (join) neilv
05:02 (quit) neilv: Changing host
05:02 (join) neilv
05:40 (quit) masm: Ping timeout: 272 seconds
06:02 (join) masm
06:19 (join) writer
06:19 (quit) writer: Changing host
06:19 (join) writer
07:40 (quit) rbarraud: Ping timeout: 252 seconds
08:02 (quit) Lajla: Ping timeout: 252 seconds
08:22 (join) hanDerPeder
08:26 (join) Lajla
09:19 bremner: someone should be keel-hauled
10:05 neilv: yeah, i had to blog about that atrocity
10:10 (quit) hanDerPeder: Quit: hanDerPeder
10:12 (join) hanDerPeder
10:16 bremner: In
10:16 bremner: Pirate talk?
10:24 (join) anRch
10:25 chandler: neilv: Mind sharing the link to this?
10:26 chandler: Oh, I've found it: http://www.linuxjournal.com/article/5487
10:26 neilv: just a throwaway blog rant about the perils of pirate-speak.  http://www.neilvandyke.org/weblog/2010/09/#2010-09-19
10:26 neilv: ah
10:27 chandler: Yes, I was looking to boggle further at the original and you didn't provide a link to it in your blog. :-)
10:27 neilv: to make this racket-relevant, someone should whip up a "#lang pirate" that renames some standard identifiers
10:28 chandler: Or a "#lang typed/pirate" that makes you walk the plank if you try to compile code containing a type error. :-)
10:32 neilv: i would suggest a drracket easter egg that pirate-ifies any error messages that occur on pirate talk day. except i just denounced that sort of thing
10:35 (quit) hanDerPeder: Quit: hanDerPeder
10:52 (join) b-man_
10:56 (join) hanDerPeder
11:00 (quit) b-man_: Ping timeout: 255 seconds
11:00 (join) b-man_
11:12 (quit) neilv: Quit: Leaving
11:19 (quit) b-man_: Remote host closed the connection
11:21 (quit) anRch: Quit: anRch
11:31 (quit) hanDerPeder: Quit: hanDerPeder
11:43 (join) hanDerPeder
11:53 (join) jonrafkind
11:55 (quit) hanDerPeder: Quit: hanDerPeder
13:00 (join) jao
13:40 (join) b-man_
13:41 (join) shofetim
13:45 (join) acts_as_david
13:52 (quit) b-man_: Read error: Connection reset by peer
13:58 (join) b-man_
14:07 shofetim: Hello, I am trying to make a tcp connection to a debugging port on google-chrome. I am using tcp-connect, and can start a connection and send info to chrome. But when I try and read from the tcp input port racket just hangs...
14:07 lisppaste: shofetim pasted "V8 connection attempt" at http://paste.lisp.org/display/114682
14:07 shofetim: at (read-line in) racket hangs...
14:08 shofetim: I'm pretty new to scheme and I don't know whats up...
14:08 shofetim: any ideas?
14:13 offby1: shofetim: maybe Chrome has nothing to say.
14:13 offby1: shofetim: I'd practice with the command-line program "nc"; that's an easy-to-use all-purpose socket thingy.
14:14 offby1: i.e., connect to nc instead of chrome, until you're certain that your racket stuff is working properly.
14:15 shofetim: K. Its the "expected behavior" then for racket to wait until there is something to read? (if a read request has been sent)
14:19 shofetim: thanks offby1 : )
14:21 offby1: I assume it's expected.
14:21 shofetim: : )
14:21 offby1: In other words, if you've told racket to read from the socket, and the process on the other end hasn't yet written anything to it, then racket will indeed hang.
14:21 chandler: Is it possible that the handshake isn't being sent?
14:21 offby1: You can make it do the other thing -- return immediately regardless -- but that's not the default, and I forget how to do it.
14:21 chandler: Since this uses TCP, you might want to use WireShark to trace what's going on.
14:22 shofetim: chandler It is being sent (I used wireshark)
14:22 shofetim: and I think its chrome is saying stuff, but not sure yet.
14:23 shofetim: I thought read-line should return or error
14:23 shofetim: so I thought I had the scheme code wrong
14:23 chandler: No; `read-line' will block.
14:23 shofetim: : ) Cool.
14:23 shofetim: by the way is "\r\n" the correct way to do a CRLF?
14:24 offby1: yep
14:24 shofetim: : ) thanks!
14:24 offby1: "\r\n" isn't just "the correct way to do" a CRLF; it _is_ a CRLF.
14:24 offby1: \r being carriage return, and \n being line feed, don't you see.
14:24 offby1: *sigh*
14:25 shofetim: yes, but (write "Message\r\n" out-put-port) doesn't write a CRLF for me
14:25 offby1: why do you say that?
14:25 shofetim: but (display "Message\r\n" out-put-port) does...
14:25 offby1: why do you say that?
14:26 shofetim: I try it, and then open the file, and in the file is the string "Message\r\n"
14:26 shofetim: not MessageCRLF (ie Message followed by a newline)
14:28 shofetim: Other languages I am used to have a different behavior for "" and '' quoted strings, so I thout it was something like that, but that doesn't seem to be how scheme does it.
14:28 shofetim: But things work with (display )
14:29 chandler: If you're working with strings, you probably want to be using `write-string'.
14:30 chandler: offby1: Using a literal \r\n in a string isn't the right way to get a CRLF in every language. Sometimes the right thing is to use '\n' and set a newline translation mode to CRLF.
14:30 shofetim: What the differance between display, write, and write-string?
14:30 chandler: So, it's a fair question to ask.
14:30 chandler: shofetim: I think you already found the difference between `display' and `write'.
14:30 chandler: rudybot: (display "Hi!")
14:30 rudybot: chandler: with Carbon Emacs, I could get true full screen, no OSX menu at the top or anything.  Pure Emacs filling my display.  With the Cocoa build in 23, maximizing the window is the best you can do, you still see the OSX menu and top of the Emacs.app window
14:30 chandler: Gah.
14:30 chandler: rudybot: eval (display "Hi!")
14:30 rudybot: chandler: your racket/load sandbox is ready
14:30 rudybot: chandler: ; stdout: "Hi!"
14:31 chandler: rudybot: eval (write "Hi!")
14:31 rudybot: chandler: ; stdout: "\"Hi!\""
14:31 chandler: There's an extra level of quoting there, so beware.
14:31 chandler: rudybot: eval (write-string "Hi!")
14:31 rudybot: chandler: ; Value: 3
14:31 rudybot: chandler: ; stdout: "Hi!"
14:31 chandler: rudybot: eval (display 42)
14:31 rudybot: chandler: ; stdout: "42"
14:31 chandler: rudybot: eval (write-string 42)
14:31 rudybot: chandler: error: write-string: expects argument of type <string>; given 42
14:32 offby1: don't get him angry
14:32 shofetim: Thnks. So writing a string to an output port (which is an out port from tcp-connect)
14:33 shofetim: with (write-line) would be the correct way to do it?
14:33 shofetim: write-string
14:34 chandler: I'd define a procedure which accepted a string and wrote that string followed by a CRLF.
14:34 chandler: Something like:
14:36 chandler: rudybot: eval (define (write-line-with-crlf (string (port (current-output-port))) (write-string string port) (write-bytes #"\r\n" port))
14:36 rudybot: chandler: error: eval:1:0: read: expected a `)' to close `('
14:36 chandler: Gr.
14:36 chandler: rudybot: eval (define (write-line-with-crlf string (port (current-output-port))) (write-string string port) (write-bytes #"\r\n" port))
14:36 chandler: rudybot: (write-line-with-crlf "Foo!")
14:36 rudybot: chandler: eh?  Try "rudybot: help".
14:37 chandler: rudybot: eval (write-line-with-crlf "Foo!")
14:37 rudybot: chandler: ; Value: 2
14:37 rudybot: chandler: ; stdout: "Foo!\r\n"
14:38 shofetim: Thanks chandler : )
15:00 (join) hanDerPeder
15:52 (part) shofetim: "ERC Version 5.3 (IRC client for Emacs)"
16:05 (join) asumu
16:46 eli: offby1: The reason for the few-days old build log is some problem in the installation step -- likely what you're running into...
16:54 (join) Quetzalcoatl_
17:20 (quit) acts_as_david: Quit: acts_as_david
17:21 writer: the serpent :)
17:48 (quit) dzhus: Ping timeout: 272 seconds
18:59 (quit) jonrafkind: Ping timeout: 240 seconds
19:02 offby1: aaah
19:44 (join) shofetim
20:15 (quit) masm: Quit: Leaving.
20:29 (part) shofetim: "ERC Version 5.3 (IRC client for Emacs)"
20:52 (quit) b-man_: Remote host closed the connection
20:55 (quit) hanDerPeder: Quit: hanDerPeder
20:59 (join) rbarraud
21:47 (join) acts_as_david
22:15 (quit) acts_as_david: Quit: acts_as_david
22:31 (join) jonrafkind
22:39 (quit) jonrafkind: Quit: Ex-Chat
22:39 (join) jonrafkind
23:04 (quit) writer: Quit: writer
23:25 (quit) Quetzalcoatl_: Quit: Leaving
23:28 (join) chadwick
23:29 chadwick: Would anyone be able to answer a Racket handin-server question?
23:34 (quit) chadwick: Quit: Page closed
23:37 jonrafkind: not anymore