World: r3wp

The sandboxing functions (*-THRU) require it. The public directory 
should only be created in the View user directory, %appdata%\REBOL 
by default.

shouldn't it only be created when *-thru is used?

*-thru is used at startup.

>> help "thru"
Found these words:
   do-thru         function! Do a net file from the disk cache.

   exists-thru?    function! Checks if a file is in the disk cache. 
   Returns: no...

   launch-thru     function! Launch a net file from the disk cache.
   load-thru       function! Load a net file from the disk cache.

   path-thru       function! Return a path relative to the disk cache.

   read-thru       function! Read a net file from thru the disk cache. 
   Returns ...

Doesn't bode well for read only media

Or an os where you don't have write permissions

You can include settings on read-only media, even start with -i if 
necessary. It's made to be adjustable.

We need to take that into account when tweaking the installer though.

I'll check if there's a setting that can go in %rebol.r that can 
disable installing, or set View to portable app mode.

When last I checked 2.7.7 allows you to run without installing if 
you tell the installer that's what you want. And there's -i.

hi,

does rebol sending email attachments inline or multipart attached?
is there any solution to have a choise? 

since a mailserver upgrade I having trouble sending a pdf as send/attach 
...

adding a content-type header or content-disposition doesn't change 
anything. encoding base 64 either not.

Sends multipart attached ...

thx graham, any  idea to change this to inline?

What I suggest you do is send an email with attach and trace it using 
wireshark.  Then do the same with an email client and see what the 
difference is.

I don't really know anything about inline attachments

I presume that inline attachments are just attachments referenced 
inside the emal using some UUID.

thx for the hint graham

I used latest R2 to do experiment something with rebol yesterday.. 
I saw the map-each function but I didn't find the accumulate . Is 
it under some other name maybe?

ACCUMULATE didn't make the cut for R3 - it will be in the /Plus library. 
An R2 version is in R2/Forward, near the end of the file.

Posted mezzanine changes for 2.7.8, ported from R2/Forward 2.100.80.0:

- Added COLLECT-WORDS, RESOLVE, SINGLE?, IMMEDIATE!, INTERNAL!, INVALID-UTF?,
  CD, MORE, and the convenience words LS, PWD, RM and MKDIR.

- Removed buggy binary! support from ASCII? and LATIN1?, as done 
in 2.100.60.


See mezz-control.r #6763, mezz-file.r #6776, mezz-series.r #6772, 
mezz-string.r

#6773 and mezz-reflect.r #6771 for the relevant changes. Details 
in R3's docs.


Note: The APPEND and REMOLD rewrites are too awkward to incorporate 
without a

native APPLY function. UNBIND hasn't been written yet (hoping for 
a native).

They're in chat. If you're interested please review the changes, 
or complain here if you like.

How about a web page?  Not everyone who uses R2 is on chat .. in 
fact most are not

Isn't the documentation system able to generate docs automatically 
 from help?

We can ask Carl about that. The R2 docs aren't updated yet afaik, 
aside from the format conversion that Carl just went through.

R2/Forward doesn't have a web page - all the docs are in the source, 
or the R3 docs. The R3 docs should work for almost all of the functions 
in R2/Forward, at least to the extent that the R3 docs are current 
and complete.

Realistically R3 is not going to be stable for another year or more 
... so the R2 docs should be updated

Realistically we need a policy for how much of the R2 and R3 docs 
are going to be shared, to avoid duplicating work. There is a discussion 
about that on Carl's blog now. Once we have a policy we can organize 
and update the docs.

All of the new functions in 2.7.7 and 2.7.8 (except THROW-ERROR) 
are backports from R3 - that is the development path for new R2 mezzanine 
functions. The rest is fixes and/or improvements to existing functions.

The same will likely be the case for future releases too, at least 
in the areas where R2 and R3 are comparable (not GUI, database, ports, 
/Library, etc.). Well see though.

Anyone who is directly participating in the development of R2 is 
in chat - that's where the source is submitted. That doesn't rule 
out indirect participation though, in the form of forwarded fixes, 
feedback, advice, bug tickets, whatever :)

>> do %json.r
Script: "JSON to Rebol converter" (21-Apr-2008)
>> text: {print "hello"}
== {print "hello"}
>> a: rebol-to-json make object! [ t: text ]
== {{"t": "print \\"hello\\""}}
>> json-to-rebol a
** User Error: Invalid JSON string. Near: <end of input>
** Near: json-to-rebol a

Gregg??

Graham I suggest you use Chris's http://www.ross-gill.com/r/altjson.html
  text: {print "hello"}              
;   {print "hello"}
  a: to-json make object! [ t: text ]
;   {{"t":"print \"hello\""}}
  probe load-json a                  
make object! [
    t: {print "hello"}
]

sounds like a good idea!

Looks like there is an escaping bug in rebol-to-json. I'll look into 
it.

I have a fixed version of %json.r. Do you want it Graham? I'll also 
send it to Douglas Crockford to post on JSON.org.


Thanks for catching that. The naive escaping has been there all along.

Hey, can you move this to Core, JavaScript or Parse? This group is 
for discussing R2 releases.

Sure thing.

No offense intended, thanks.

None taken.

Any reason why I can't change this http://rebol.wik.is/Protocols/Secure_Smtp
from

			port/user: port/user
			port/pass: port/pass
			; do authn if needed

to
			; fix: only ask once if the user used set-net ask
			port/user: system/schemes/esmtp/user
			port/pass: system/schemes/esmtp/pass

so I don't have to fix set-net as well??

Why secure does not accept

Why secure does not accept block! argument?
secure [net allow] ;works
b: [net allow]
secure b ;fails

try  "secure :b"

it works! thanks a lot. But it is not documented in core.pdf

>> secure b
** Script Error: Invalid argument: b
** Near: secure b
b was treated as a word like 'allow   'ask ,
so use :b instead, to get its value

I see. but help text says it accepts word! and block! so it is confusing.

the feature of rebol that function can accept a word without evaluating 
it even if it's an action word makes rebol more nice to look at but 
at cases as this it can cause confusion

without it you would have to ad ' in this case, liek this >> foreach 
'item block [ print item ]

it's a little less nice looking but it would be more uniform and 
logical .. the way of "least surprise"


because now when you write your own functions liek map-each you don't 
know or make it look like foreach with or make all custom functions 
not accept active words which makes your code more systematic and 
easyer to understand , but then your function is not in style with 
rebol's foreach forall ..etc