World: r3wp

end of is not correct name. End is end, period :-) 'remove last-of 
series' would be OK though ...

Ladislav, note that on Unix, the TOUCH command creates the file if 
it does not exist. so I would not necessarily consider that a bug...

Ladislav: also, I think OPEN without /DIRECT will actually read the 
file and then write it back, so it's no different from Geomol's solution 
actually. Gregg's /SEEK/BINARY (actually I think /SEEK implies /BINARY) 
should work better.

I do not consider it a bug, but I do want a different behaviour, 
which I have to simulate somehow

Ladislav, yes I saw corruption.

And performance memory issues on large files.

So, I need to send seme emails and need to login into my SMTP server. 
And this mostly fails out-of-the box in Rebol 2 and I can't remember 
what to do to make it work:

>> send [robert-:-muench-:-googlemail-:-com] "Test"
Net-log: ["Opening" "tcp" "for" "esmtp"]
connecting to: mail.saphirion.com
Net-log: [none "220"]

Net-log: {220 mail.saphirion.com ESMTP Exim 4.63 Sat, 09 Oct 2010 
12:12:46 +0200}
Net-log: [["EHLO" system/network/host] "250"]

Net-log: {250-mail.saphirion.com Hello mail.saphirion.com [10.0.0.3]}
Net-log: "250-SIZE 52428800"
Net-log: "250-AUTH LOGIN CRAM-MD5 DIGEST-MD5"
Net-log: "250 HELP"
Net-log: ["Supported auth methods:" [login cram]]
Net-log: ["MAIL FROM: <[robert-:-muench-:-saphirion-:-com]>" "250"]
Net-log: "250 OK"
Net-log: ["RCPT TO: <[robert-:-muench-:-googlemail-:-com]>" "250"]
** User Error: Server error: tcp 530 Relaying not allowed
** Near: insert smtp-port reduce [from reduce [addr] tmp]


I think the probem is that Rebol isn't logging in correctly. Either 
it doesn't understand the supported methods or something else is 
different. Any ideas how I can fix it or track it down?

0.k='45

?

Sorry I forgot to decompress the message:


I have no problem sending from an ESMTP account from Rebol after 
setting the account name and password with set-net:

? set-net is pretty self-explanatory.

You could possibly get this message if you are not directly connected 
to the ISP hosting saphirion.com.

I found this explanation helpful :

http://www.answersthatwork.com/Download_Area/ATW_Library/Networking/Network__3-SMTP_Server_Status_Codes_and_SMTP_Error_Codes.pdf

If it's neither of those this script at REBOL.org may be of help 
:

http://www.rebol.org/view-script.r?script=patch-esmtp-net.r

whats the easiest way to assign a block of values to a block of words? 

fields: [ref lname fname]
data: [1 "Smith" "Bob"]

set fields data

thanks

lol

:-) had amacleod not been a REBOLer, he might have said "stop making 
jokes".

awesome :-)

I've been assigning them one at a time this whole time...feel like 
a dope

Hard time to pass by, don't worry, we sympatize :-)

this creates globals though

And in R3, it will bypass the setting of locals with funct

and in R2 using the r2/forwards

he ? SET doesn't modify the bouding context of the words

>> unset 'crap
>> context [ set [ crap ] [ 1 ]]
>> crap
== 1

so what ? you didn't declare 'crap in the context.
SET doesn't modify the context.

>> global: 1
== 1
>> do test: funct [ ][ set 'global 2 ]
== 2
>> global
== 2

so what ? you didn't declare 'crap in the context.
SET doesn't modify the context the words.

I'm saying that if you use the set method, then your words appear 
in the global context which you may not want

So what ? you don't declare 'crap in the context.
I repeat: SET doesn't modify the context of the words.

Here  it's local.
>> c: context [crap: 0 set [crap] [1]] c/crape
== 1

Sorry for the echo, my connection is bad currenlty

It's Altme ....

I think Graham simply wants the block to be set within the context 
with as little additional code as possible.

If you want to use the set method of whole sale settting variables 
you have to declare them first in the context to prevent them from 
becoming global.  So what gain is there?

unless you do something like this

use fields [
	set fields data
]

this creates globals though

 - this is actually wrong, SET does neither "create", nor "globals"

And in R3, it will bypass the setting of locals with funct

 - in R2, as well as in R3, when using the SET function, you bypass 
 the collection of object locals. In R3, with FUNCT, you may not bypass 
 the collection as follows:

set [a: b:] [1 2]

neat trick

because 'funct scans the body of the function looking for set-words

Actually, I already used the trick in R3

with collect-words, an handy function, not well known

native by the way

COLLECT-WORDS is a native, but it is quite easy to define it in R2 
as a mezzanine

but not soo fast indeed :-)