World: r3wp

pekr, its a console application, just like our current R3 CLI.   
a console is simply a place which accepts lines of input interactively 
and spawns processing upon hitting a complete command.

a shell is a different thing entirely.  though the shell usually 
has access to the same input stream which is re-directed to/from 
the console.

But you'll probably need some hostkit hacking in any case.

http://www.rebol.net/cgi-bin/r3blog.r?view=0282#comments

Andreas - power console can't work. I tried Console2. The outcome 
is, you can't have both the true console mode and the GUI app. Look 
at the above link. Or simply Carl was not able to achieve that. Some 
ppl said, that is the reason why Python has two executables - one 
for plain console mode, and the other for GUI mode. But I might not 
interpret it correctly ...

Max - sorry for mispelling console for shell ...

Fortunately, with the hostkit you have the power to compile either 
as console or windows app.

IIRC, R3 is currently compiled as console app per default.

So currently "installing a proper shell" should work.

coundn't we just use their better console handling code and use it 
within R3's input loop?  or is that part of what you really meant?

yes? then we should take car to make it work with real console. I 
don't need power-shell. Shell2 is nice and sufficient. Simply - anything 
better than MS default console, is a win ...

http://sourceforge.net/projects/console/

What I mean is, two options:

- Short term: use a third-party shell replacement (like rxvt, console2, 
...)
- Long term: let someone write a nice R2-style console

recently even the short-term is not done ...

short term == now!

Damn, do I really have to fire up a Windows VM just to test if this 
is really possible right now :) ?

how should I test? launch cmd.exe, and type R3? :-)

hmm, it launches new console, instead of using existing one ...

Bad :)

A108?

nooo, A107 ... and btw - what about that security dialog? Still no 
answer why it happens ...

tried A108 from console, and got:

** Script error: clean-path word is not bound to a context
** Where: if -applier-

** Near: if slash <> first boot [boot: clean-path boot] home: file: 
f...

Wow, that must be the error Brian mentioned.

I assume you tried the RT binary A107?

Would you be so kind and try http://bolka.at/2010/rebol3/r3-a107-20100913.exe
instead?

RT binaries are built as GUI apps, the above is built as Console 
app.

Pekr, we found that error too and fixed it for the next release.

A109 for Win32 released:
http://www.rebol.com/r3/downloads/r3-a109-3-1.exe

launch from cmd.exe is fixed. Although I would like to see R3 to 
reuse cmd console, if it does not include GUI ...

Pekr, did you try the custom-built A107 binary I linked to above?

not yet, let me try ...

:-) http://xidys.com/rebol/r3-console2.jpg

I can even start view scripts ;-) I suspect it being so, because 
view is not externalised? So could we now conclude, that from now 
on, R3 could be built as a console app?

Yes, it is a "View" build.

And yes as well, until R3 gets an R2-style REBOL console, building 
it as Win32 console executable might be worth it.

However, ChristianE hat some problems with Unicode in combination 
with console builds, IIRC.

had*

Not sure what that was about though. Maybe Christian remembers, otherwise 
I'll have to recover the lost !REBOL3 Hostkit from backup.

yes, you can see in the screenshot, that czech locale is not correct 
...

from my experience, if I build R3 as 'console app' the win console 
(the way it is handled now)  doesn't render characters in unicode. 
So far I haven't found a way how to fix that (and after brief googling 
the net it looks this is known issue)

that's bad :-(

Cyphre, Andreas, that's what I was seeing, too. Build as console 
app --> no unicode chars displayed, build as gui app --> unicode 
chars are fine, but you can't run in a console window. I don't know 
what other languages are doing or if there is a way to fix this at 
all. From the information I gathered back then, I'd say, probably 
there isn't.

imo, for the 'console app'  version you would need to use different 
approach...detect if the process already have console attached and 
the reuse it. But I  haven't looked into any details so it is possible 
even this won't work well.

Cyphre - we are already reusing the console (I mean - Andreas, I 
just do some tests). We can even get czech chars displayed, byt typing 
czech chars firing enter quits R3 ...

ok, that is in the 'console app' mode....sorry I meant that there 
might be a way how to check if the 'GUI app' is run standalone or 
from console and then decide what approach to use. But I haven't 
tried to play with it yet.

yeah, that would be interesting.

unfortunately there seems to be no way for a GUI app to keep an association 
to the console it was launched from.

you can try to attach to the console of the parent process, but carl 
seems to have tried that and it is now disabled for some reason.

well, needs further investigation :)

The reason was the blog article I posted - see the comments ...