World: r3wp

print length? s

print pick s 1

stuck at the open

could you try and replace `wait either system/version/4 = 4 [1] [subport]` 
by just `wait 1`

that works

interesting

>> write mbox "RETR 1"
write
** Script error: copy does not allow char! for its value argument
** Where: write
** Near: write mbox "RETR 1"

you need []

and the first item must be solely the command

eg

`write mbox ["RETR" 1]` should work

shouldn't state always be set to 'retr after all write commands?

ie. you always want to get the response until you hit the "."

that's only for multiline commands

or a "+OK" or a "-ERR"

STAT, DELE, RSET only have one-line responses

NOOP

QUIT

(for example, yes)

actually, WRITE exposes the low-level interface here

for RETR, PICK would be the high-level interface

cause I get nothing back aftre

write mbox [ "RETR" 1 ]

etc

read mbox

and you'll get whatever the command handler deems to be the right 
result to pass along

ahh....

write mboxc [ "TOP" 1 10 ]
hangs :)

after the read ...

obviously, as there's no top handling yet :)

write mbox [ "TOP" 1 10 ]
read mbox

not the way it's suposed to work?

I see the top 10 lines and a "."

yes, in the debug output :)

open, length?, pick, close -- that's the currently supported interface

ok :)

open? is also supported

Just needs a little error handling ...

yep

schemes aren't so hard :)

and an async mode, of course :)

nope, they are rather nice :)

actually, if you want TOP to work, you can use the internal write/read 
as well

ah, no, you can't. my mistake :)

well, I was just thinking that it should work as I tried it :)

you send the command to the port and retrieve either a multi or single 
line response

write is not really intended for the user

i think that all common commands should be supported by nice higher 
level wrappers

Sure ... but then a new command comes along ...

say I want to UIDL ?

exactly, that's when you'd use write/read directly

+OK, what's next ?   Ftp :)