00:00:00 --- log: started forth/18.02.03 00:08:49 --- quit: dys (Ping timeout: 240 seconds) 00:11:00 --- join: dys (~dys@tmo-123-31.customers.d1-online.com) joined #forth 02:05:04 --- quit: groovy2shoes (Ping timeout: 276 seconds) 02:12:19 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:53:15 --- quit: proteus-guy (Read error: Connection reset by peer) 03:53:44 --- join: proteus-guy (~proteusgu@183.88.80.18) joined #forth 03:55:01 --- join: tomlukeywood (~quassel@host-92-19-232-58.static.as13285.net) joined #forth 04:08:37 --- join: ncv__ (~neceve@unaffiliated/neceve) joined #forth 05:01:34 --- quit: tomlukeywood (Remote host closed the connection) 05:43:24 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 05:46:53 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 06:37:23 --- join: Labu (~mik@mvice.pck.nerim.net) joined #forth 06:37:51 Hello 06:43:28 Labu: hi 06:47:08 --- quit: nighty- (Remote host closed the connection) 08:11:44 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 08:26:18 --- join: tomlukeywood (~quassel@host-92-19-232-58.static.as13285.net) joined #forth 08:33:19 --- quit: tomlukeywood (Remote host closed the connection) 09:46:36 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 10:08:30 --- join: yuoip (2d1f5dab@gateway/web/freenode/ip.45.31.93.171) joined #forth 10:48:05 --- join: gravicappa (~gravicapp@ppp83-237-167-241.pppoe.mtu-net.ru) joined #forth 11:20:19 --- join: beretta (~beretta@cpe-184-58-116-76.columbus.res.rr.com) joined #forth 11:32:18 --- quit: ncv__ (Ping timeout: 256 seconds) 12:11:03 --- quit: dys (Ping timeout: 248 seconds) 12:12:05 --- join: dys (~dys@tmo-106-195.customers.d1-online.com) joined #forth 13:00:51 --- quit: gravicappa (Ping timeout: 256 seconds) 13:34:47 --- join: MrMobius (~MrMobius@c-24-3-221-208.hsd1.wv.comcast.net) joined #forth 14:06:45 --- part: yuoip left #forth 14:36:50 --- quit: Darksecond (Read error: Connection reset by peer) 14:40:07 --- join: Darksecond (~darksecon@a82-94-53-70.adsl.xs4all.nl) joined #forth 15:06:43 --- quit: beretta (Ping timeout: 264 seconds) 15:24:48 --- quit: johnmark (Quit: Leaving) 15:46:03 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 18:06:20 --- quit: Labu (Quit: Leaving.) 20:14:51 --- join: smokeink (~smokeink@59-125-75-78.HINET-IP.hinet.net) joined #forth 20:19:00 --- quit: dddddd (Remote host closed the connection) 21:20:07 --- quit: Gromboli (Quit: Leaving) 21:35:33 --- quit: lijero (Remote host closed the connection) 21:41:44 --- join: beretta (~beretta@cpe-184-58-116-76.columbus.res.rr.com) joined #forth 22:08:35 --- quit: ovf (Disconnected by services) 22:08:58 --- join: pointfree_ (sid204397@gateway/web/irccloud.com/x-kdjdkvamerbbshzt) joined #forth 22:09:38 --- join: ovf (sid19068@gateway/web/irccloud.com/x-bxccivbjuwkvlxaa) joined #forth 22:14:41 --- join: wibblewiggy1981 (8269cf3c@gateway/web/freenode/ip.130.105.207.60) joined #forth 22:15:55 --- quit: pointfree (*.net *.split) 22:15:56 --- quit: ggherdov` (*.net *.split) 22:16:08 --- nick: pointfree_ -> pointfree 22:17:35 Hi I am really enjoying using gforth, I managed to figure out how to use blocks and extended the screen editor. But what I am trying to do is position an ascii box using at-xy on the screen using a nestled do loop. My problem is I can get the size of the box to work at the side of the terminal. The problem is I am using CR to complete the loop. Is there a way I can print 16 lines of 64 spaces without using CR in the loop? 22:23:34 use at-xy with an increment? 22:24:32 @ koisoke, yes but I am getting a bit confused with the variables. I have the pastebin here.. https://pastebin.com/emgFKxAy 22:25:56 which part specifically 22:27:22 @ koisoke should I use local variables with this or just stick to global ones? I want to try and keep the program tidy. Thats why I have been getting into problems because its a bit of a mess at the mo. Its the outer loop. I want to decrement the position on the terminal, and set that as the new value for at-xy to use to point at, then print the spaces, then for as many lines as needed repeat. But should I use a tempoary vari 22:30:34 you got cut off after "But should I use a temporary vari.." 22:31:38 @ koisoke .. ah sorry. Should I just duplicate the orignal variable on the stack or use a tempoary variable to handle this. What I want is the word to use start_x start_y to get the postion to draw the window. 22:33:09 matter of personal taste i guess. i would probalby put things like that that track global state of the renering engine in a variable 22:33:19 *rendering 22:33:58 I guess an array to hold the various parameters for the windows would be a good idea? 22:35:36 I looked through the block editor source you showed. The plan is to have two lists open, the first being the open block and the second being the help screen... 22:37:48 i guess an array with accessor words would work. 22:38:14 i can't believe you're actually using that block editor :D it is terrible 22:47:26 --- quit: smokeink (Remote host closed the connection) 22:48:19 I will update it with a nice interface, the ability to see many blocks at once.. it will be nice. 22:48:20 :) 22:48:22 --- join: smokeink (~smokeink@n11212033249.netvigator.com) joined #forth 22:50:08 good luck :) 22:50:34 i think the bigforth one had a nicer interface. haven't looked at portability issues 22:50:50 (nor at that editor at all in ages) 22:52:10 it was ok I just thought it needed a little pizaz with the colour. 22:53:58 so under the hood does file handling work the same way as the buffer flusing with blocks? I could see using blocks as a way to avoid hammering somthing like a flash memory. 22:55:38 not typically afaik. generally a pretty thin layer over the libc functions on modern oses 22:56:32 That's what I suspected. 22:56:55 *clutching at straws... well its nice to know exactly how much each block takes up... 22:59:53 Oh can I ask, is there a way to make system calls that are non-blocking? 23:03:11 to otherwise blocking system calls? would need threads 23:03:34 i haven't loked into gforth's thread support 23:04:06 yea what I wanted to do was say open a pdf from within the program then hand control back to the program while evince is still open. 23:04:20 at the moment i have to close the application 23:04:33 so like, fork and exec 23:05:13 ahhh i am a big dummy yes exactly like that 23:05:20 I want to spawn them as child processes 23:05:46 that way the block editor can act as a kind of IDE, then launch the emulator to run the code that it generates. 23:07:59 last time i did anything like that, which was awhile ago, i used a little program written in C and communicated with it via a shared memmap. though a socket owuld probably be the more sensible thing there 23:08:55 gforth does sort-of have a foreign function interface but i haven't used enough to endorse it other than blindly 23:09:21 I been thinking about ffi but there is not so much info on it. 23:09:27 I like the socket idea though 23:09:32 that seems a very solid aproach 23:09:50 it's just >1 thing to launch and a bunch of code in C 23:11:20 hmm will have a think about this. 23:14:20 the next stage was chunking the terminal output ala color forth with the words having diffrent text colour but that is the next step.. 23:30:21 --- nick: fiddlerwoaroof_ -> fiddlerwoaroof 23:59:59 --- log: ended forth/18.02.03