World: r3wp

I will ...  with  a nice recipe for disaster as an example  hehehe 
   ;-)

Carl wanted us to set-up new wish ticket, if we think it is wrong 
...

might as well go all the way ....

date/iso8601

Maybe Cygwin could be a use as a console for REBOL under Windows? 
Libraries like this could be used then:
http://www.astro.caltech.edu/~mcs/tecla/index.html


I can't imagine a serious developer would be ok with the default 
Win console and no history and such.

Max - have you added your ticket? I can see it as a serious problem, 
so if you don't post it, I'll do ....

Geomol, the default Windows console has history, both in terms of 
a screen buffer and command line history.

Can't the problem with the console be posted to stackoverflow? There 
might be a few Windows experts out there willing to help

maybe Carl would be too proud to let part of the implementation of 
REBOL be influenced by a stackoverflow answer :-)

Why not to look into Python, Perl, Ruby etc. sources?

we reallly need to get 'SUM into R3... its just  soooooo slow to 
sum values in a block using rebol iteration.

as in
>> SUM [ 1 2 3 4]
== 10

same for block oriented 'MIN and 'MAX

(*** As natives***)

>> MIN-OF  [ 1 2 3 4]
== 1

>> MAX-OF  [ 1 2 3 4] 
== 4

pekr, add the ticket, this way Carl will realise I'm not the only 
one with some reserves as to current implementation of new date!/hour 
accessor

Geomol, the default Windows console has history, both in terms of 
a screen buffer and command line history


Yes, I just noticed that today, when I tried under Windows. What 
exactly is the problem? The pasting of text into the console could 
be better, I think.

Max - Carl objected a bit to my ticket, so please ad your comment 
there at least :-) http://curecode.org/rebol3/ticket.rsp?id=1308&cursor=1

done.

R3 produces an syntax error, when loading Umlaut in strings, but 
shows the correct string in the error message.
e.g

>> load %test
** Syntax error: invalid "string" -- "{ö}"
** Where: transcode either if load
** Near: (line 1) {ö}


I know, the problem has to do with the unicode extensions of R3, 
but it should be at least configurable, if R3 works with unicode 
by default..

hmm, interesting. R3 scripts should be UTF-8 by default, but dunno 
if it should, or should not work ...

see why I'm not using R3 yet  ;-)

that's a little problem ...

Showing the correct character in a string might be a console font 
thing. Is %test encoded in UTF-8?

The syntax scanner has been accumulating a set of changes that need 
fixing. I would guess that Carl wants to do them all at once, since 
fixing the scanner is apparently not an easy task. It might be hand-made.

shouldn't it be put in CC though?

ah, it's there ...

%test is ISO8859 decoded as default

hi, i try to explore tcp on R3 with an telnet scheme !!!!   i try 
 ;-)

wp: make port! tcp://user:[pass-:-telnetserver]:23
wp/awake: func [event /local port] [
    port: event/port
    print ["==TCP-event:" event/type]
    switch/default event/type [
        read [print ["read:" length? port/data] read port]
        wrote [read port]
        lookup [print query port open port]
        connect [write port {ls -lisa}]
    ][true]
]
open wp
wait [wp 5]
print wp/data
close wp

i try to have "ls -lisa echo" from telnet but a obtain only {} !!! 
why

thank in advance

http://www.rebol.org/view-script.r?script=telnet.r

ooop ... R3 group

a94 released with 21 bugfixes

the /hour refinements where changed to reflect timezone   :-D   


goes to show we have a lot of voice in how R3 evolves... when we 
can provide concrete arguments.

Damned Windows. The heritage of old DOS is still present, resulting 
in one thing - we can't have good default console with R3. As http://curecode.org/rebol3/ticket.rsp?id=1305&cursor=7
was dismissed, we really need new console in R3 - no need to keep 
the default black crap Windows provides ...

If we don't get it, this one feature deeply degrades R3 experience 
for me - no tab completion, no multiline string, not freely resizable 
- current R3 console is of absolutly unacceptable quality for me. 
We need at least R2 level of console ...

there is nothing stopping Carl from adding the R2 console back into 
R3.  the current.exe is still a GUI app.

which is why he speaks about making another .exe which starts up 
in console mode.

I had many problems running sdk command-line apps when doing client 
work a few years ago... now at least this whole issue can be addressed, 
by simply flicking a switch in the host code and compiling a console 
version  :-)

I am really not satisfied with the Comments of Carl to #0001309 .
If I should read/as, I have to patch do and load and whatever.
I woud prefer a setting in the system/options.

I also think the "default" user text format should be configurable. 
  I have absolutely no desire to start using utf-8 for my code and 
data, especially when I have a lot of stuff that already is in iso 
latin-1 encoding.

if in ascii, it will be loaded ok, no?

ascii is 127 bytes... we are talking about the upper 127 chars.

sqlab - how do you want to do the conversion automatically? How should 
R3 know, what code-page the script is in? Maybe we could use header 
field, and load could act uccording to it?

Ascii is 255 ;-)

you trying to tell me, I can't load upper 127 bytes?

mmnt ...

upper 127 are NOT ascii.

they are different all around the world.