<veltas> Congrats veltas you wrote a whole forth thinking ABORT" was unconditional
<lispmacs[work]> crc: I just took a look at retroforth, and was wondering: did you have some kind of long term strategy of adding system interaction functionality to the vm? like, the ability to connect to network sockets or to gfx libraries? I see your Web server example skirts that question by using inetd
<lispmacs[work]> I was just wondering because I had been pondering one day writing a forth vm that had some basic desktop system interfaces, like an interface to a graphics window
<Zarutian_HTC> lispmacs[work]: hmm... I have been thinking about this and I think just doing a vnc server in a forth on a vm that supports network sockets might be the easiest way
<Zarutian_HTC> plus it is the way least likely to bitrot
<klys> virgl > vnc
X-Scale has quit [Ping timeout: 264 seconds]
X-Scale` has joined #forth
X-Scale` is now known as X-Scale
<lispmacs[work]> Zarutian_HTC: that sounds like a pretty good solution, excepting I think the inabilty to do any graphics hardware acceleration
<crc> lispmacs[work]: on a Unix host, the VM does support sockets
shmorgle has joined #forth
<lispmacs[work]> but even without gfx hardware acceleration, it would be a big improvement over what we have now as far as a graphical desktop interface for Forth, which so far as I can tell is pretty much nothing
<crc> Graphics are an ongoing research topic at present
<crc> I've built experimental VM implementations providing a framebuffer and higher level drawing primitives, but haven't settled on anything yet. (I don't write many things that need graphical support, so it's kind of a low priority for me)
<Zarutian_HTC> klys: have not heard of virgl.
<Zarutian_HTC> one other thing vnc has going for it is the plethora of vnc viewers available
<Zarutian_HTC> klys: I see
<Zarutian_HTC> might be quite more than my requirements
<Zarutian_HTC> crc: is that framebuffer just some huge ALOTted rgba pixmap?
<Zarutian_HTC> (the alpha channel could be omitted)
<crc> Zarutian_HTC: yes
<Zarutian_HTC> then a minimal vnc server that gives access to that should not be that hard to write
gravicappa has joined #forth
<Zarutian_HTC> crc: is there an non-blocking version of socket:accept ?
<crc> Not that I've defined
<crc> The C part providing the sockets is forthworks.com:8000/file?name=vm/nga-c/dev-sockets.c&ci=tip
<crc> I'm pretty sure that all I've done in this is blocking
elioat has joined #forth
elioat has quit [Client Quit]
<crc> This is another thing I don't use very often, so my experience with raw sockets is *very* minimal
<crc> the main I've used it for is an irc bot
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
gravicappa has quit [Ping timeout: 240 seconds]
sts-q has quit [Ping timeout: 256 seconds]
sts-q has joined #forth
Zarutian_HTC has quit [Ping timeout: 265 seconds]
gravicappa has joined #forth
hosewiejacke has joined #forth
_whitelogger has joined #forth
hosewiejacke has quit [Ping timeout: 240 seconds]
hosewiejacke has joined #forth
proteus-guy has quit [Ping timeout: 264 seconds]
hosewiejacke has quit [Ping timeout: 272 seconds]
patrickg has quit [*.net *.split]
TangentDelta has quit [*.net *.split]
a3f has quit [*.net *.split]
hosewiejacke has joined #forth
TangentDelta has joined #forth
a3f has joined #forth
patrickg has joined #forth
jevinskie[m] has quit [Ping timeout: 240 seconds]
jimt[m] has quit [Ping timeout: 246 seconds]
patrickg has quit [Ping timeout: 258 seconds]
siraben has quit [Ping timeout: 244 seconds]
clog has quit [Ping timeout: 266 seconds]
joe9 has quit [Ping timeout: 246 seconds]
joe9 has joined #forth
xek has joined #forth
hosewiejacke has quit [Ping timeout: 240 seconds]
jedb has quit [Ping timeout: 264 seconds]
jimt[m] has joined #forth
jedb has joined #forth
jevinskie[m] has joined #forth
siraben has joined #forth
patrickg has joined #forth
proteusguy has quit [Remote host closed the connection]
iyzsong has quit [Quit: ZNC 1.7.5 - https://znc.in]
iyzsong has joined #forth
jedb has quit [Remote host closed the connection]
f-a has joined #forth
clog has joined #forth
hosewiejacke has joined #forth
proteusguy has joined #forth
mstevens has quit [Remote host closed the connection]
mjl has quit [Remote host closed the connection]
mjl has joined #forth
mjl has quit [Remote host closed the connection]
mjl has joined #forth
mstevens has joined #forth
hosewiejacke has quit [Ping timeout: 264 seconds]
ovf has quit [Remote host closed the connection]
jedb has joined #forth
ovf has joined #forth
ovf has quit [Excess Flood]
ovf has joined #forth
sts-q has quit [Quit: ]
sts-q has joined #forth
sts-q has quit [Client Quit]
sts-q has joined #forth
sts-q has quit [Client Quit]
sts-q has joined #forth
sts-q has quit [Client Quit]
sts-q has joined #forth
ovf has quit []
ovf has joined #forth
hosewiejacke has joined #forth
Zarutian_HTC has quit [Ping timeout: 256 seconds]
Zarutian_HTC has joined #forth
f-a has quit [Ping timeout: 265 seconds]
f-a has joined #forth
hosewiejacke has quit [Ping timeout: 256 seconds]
f-a has quit [Ping timeout: 256 seconds]
dave0 has quit [Quit: dave's not here]
hosewiejacke has joined #forth
f-a has joined #forth
Gromboli2 has joined #forth
f-a_ has joined #forth
rpcope- has joined #forth
f-a has quit [*.net *.split]
clog has quit [*.net *.split]
rpcope has quit [*.net *.split]
Gromboli has quit [*.net *.split]
lispmacs has quit [*.net *.split]
Gromboli2 is now known as Gromboli
clog has joined #forth
07IAAT6KJ has joined #forth
07IAAT6KJ has quit [Ping timeout: 254 seconds]
sts-q has quit [Ping timeout: 264 seconds]
klys has quit [Ping timeout: 272 seconds]
klys has joined #forth
jedb_ has joined #forth
sts-q has joined #forth
jedb has quit [Ping timeout: 256 seconds]
klys has quit [Ping timeout: 240 seconds]
Zarutian_HTC has quit [Read error: Connection reset by peer]
Zarutian_HTC has joined #forth
klys has joined #forth
f-a_ has quit [Quit: leaving]
f-a has joined #forth
klys has quit [Ping timeout: 264 seconds]
f-a has quit [Ping timeout: 246 seconds]
f-a has joined #forth
klys has joined #forth
klys has quit [Ping timeout: 265 seconds]
hosewiejacke has quit [Ping timeout: 272 seconds]
klys has joined #forth
klys has quit [Ping timeout: 240 seconds]
hosewiejacke has joined #forth
klys has joined #forth
hosewiejacke has quit [Remote host closed the connection]
klys has quit [Ping timeout: 256 seconds]
<f-a> `words` has a lot of words :P
neuro_sys has quit [*.net *.split]
remexre has quit [*.net *.split]
nitrix has quit [*.net *.split]
ornxka_ has quit [*.net *.split]
lonjil has quit [*.net *.split]
dzho has quit [*.net *.split]
<veltas> f-a: Defining a word to print a more manageable number at a time between key presses with TRAVERSE-WORDLIST is left as an exercise to the reader
klys has joined #forth
<f-a> hehe
remexre has joined #forth
neuro_sys has joined #forth
nitrix has joined #forth
dzho has joined #forth
ornxka_ has joined #forth
lonjil has joined #forth
lonjil has quit [Max SendQ exceeded]
lonjil has joined #forth
lispmacs[work] has quit [Remote host closed the connection]
lispmacs[work] has joined #forth
gravicappa has quit [Ping timeout: 240 seconds]
f-a_ has joined #forth
f-a_ has quit [Client Quit]
f-a has quit [Read error: Connection reset by peer]
f-a has joined #forth
<veltas> f-a: What text editor are you using?
<f-a> vim
<veltas> I'm just going to leave this here https://github.com/Veltas/forth-vim
* veltas walks out
<f-a> haha
<f-a> the hero we need
<f-a> > This is a less-visually-loud vim syntax script for Forth source code.
<veltas> The default forth syntax highlighting is quite bad in vim and I'm not the only one who has attempted to write a better one
<f-a> I literally have a «check how to make syntaxhighlight for forth less eyebleeding»
<veltas> But I was the first to get to you
<f-a> now then
<f-a> let us see
<f-a> thanks for it veltas !
<f-a> I will tweak it a bit more
<lispmacs[work]> : vim emacs ;
<veltas> f-a: No problem and please tell me if it's borken
<veltas> lispmacs[work]: : emacs ed ;
<lispmacs[work]> aren't all forth's supposed to have an awesome built-in editor
<f-a> one thing I will maybe change is that, both in yours and normal vim, \ xxx and \ todo are highlighter in yellow + reverse
<veltas> The interpreter is an editor of sorts
<lispmacs[work]> at work, I sometimes use the EDITOR program from a 1980's MPX computer. It has awesome features like the ability to overwrite only certain characters in a line
<veltas> What do you mean, "overwrite only certain characters in a line"?
<lispmacs[work]> like if the line is "red dog chases cat", you could enter " c w" to get "red cow chases cat"
<lispmacs[work]> but you have to enter a command first to enter that mode and specify the range. similiar I think to ed
<veltas> That reminds me of COPY key from a lot of 80s micros
<lispmacs[work]> the editor inserts line number's at the end of each line
<lispmacs[work]> allowing you to add lines in between lines, like in an old BASIC program
<veltas> And right-arrow from DOS I think did the same
<veltas> In ed you'd probably write s/dog/cow
<lispmacs[work]> Chuck Moore said you were supposed to write a new editor for each kind of editing task you wanted to do
<veltas> I wonder if he's used emacs
<veltas> emacs has functions to do many basic editing tasks
actuallybatman has quit [Quit: leaving]
xek has quit [Ping timeout: 265 seconds]
f-a has quit [Read error: Connection reset by peer]
f-a has joined #forth
f-a has quit [Quit: leaving]
f-a has joined #forth
f-a has quit [Client Quit]
f-a has joined #forth