00:00:00 --- log: started forth/19.09.29 00:00:24 --- quit: ryke (Ping timeout: 240 seconds) 00:47:35 --- join: iyzsong (~iyzsong@fsf/member/iyzsong) joined #forth 01:02:47 --- quit: dddddd (Remote host closed the connection) 01:40:45 --- join: inode (~inode@unaffiliated/inode) joined #forth 01:59:02 --- quit: rdrop-exit (Quit: Lost terminal) 02:24:08 --- join: nullnullnull (~nullnulln@31.154.190.34) joined #forth 02:26:27 guys, can anyone help me with line 459 (how to implement it with gforth) https://github.com/forthy42/gforth/blob/master/unix/socket.fs 02:26:43 I tried "1000 get-socket-timeout" but not working 02:27:09 1000 set-socket-timeout 02:53:13 --- quit: chunkypuffs (Quit: ZNC 1.7.1 - https://znc.in) 03:01:25 --- join: chunkypuffs (~chunkypuf@static.203.112.216.95.clients.your-server.de) joined #forth 03:24:29 what's not working about it 03:25:32 it does require an unsigned integer btw nullnullnull 04:28:48 hmm 04:29:39 WilhelmVonWeiner, can u give me an example? here's my code: 04:29:42 https://pastebin.com/4AQm2h9Y 05:30:18 --- quit: APic (Ping timeout: 240 seconds) 05:53:46 --- join: APic (apic@apic.name) joined #forth 06:29:14 --- quit: nullnullnull (Quit: Leaving) 07:01:20 --- join: ryke (~Thunderbi@148.59.249.52) joined #forth 07:11:51 --- quit: gravicappa (Ping timeout: 276 seconds) 07:16:24 --- quit: dave0 (Quit: dave's not here) 07:23:38 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 07:29:00 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 07:41:25 --- join: ryke1 (~Thunderbi@71-9-171-192.dhcp.jcsn.tn.charter.com) joined #forth 07:41:58 --- quit: ryke (Ping timeout: 240 seconds) 07:41:59 --- nick: ryke1 -> ryke 08:18:38 --- quit: APic (Ping timeout: 240 seconds) 08:36:39 --- join: APic (apic@apic.name) joined #forth 09:05:19 --- quit: cmtptr (Quit: leaving) 09:06:49 --- join: gravicappa (~gravicapp@h109-187-209-116.dyn.bashtel.ru) joined #forth 09:11:58 tp: What happened to the embello github repo? 10:55:53 pointfree, I see its 404 at the moment, perhaps the author removed it as he had dropped Forth and gone to some other language ? 11:22:22 --- join: cmtptr (~corey@unaffiliated/cmtptr) joined #forth 11:23:46 Is there a de facto website for looking up definitions for standard Forth words? I use forth-standard.org a lot but it goes down periodically which can be kinda frustrating. 11:30:09 maybe a bit extreme, but could you just download that site? 11:31:54 the standards themselves aren't too unreadable, IMHO 11:32:10 you can download them in PDF form 11:32:50 that would be much better than my idea. 11:33:53 http://dl.forth.com/sitedocs/dpans94.pdf for ANSI '94 11:36:18 --- join: xek (~xek@apn-31-0-23-83.dynamic.gprs.plus.pl) joined #forth 11:45:31 Not a bad idea. I really like the structure of the website so I may just wget it or something 12:00:09 --- quit: cmtptr (Quit: leaving) 12:04:09 oh he left 12:04:12 shame 12:04:39 also forth-standard.org/ is down with a 500 error 12:08:39 --- join: cmtptr (~corey@unaffiliated/cmtptr) joined #forth 12:50:15 --- join: dys (~dys@tmo-110-186.customers.d1-online.com) joined #forth 13:17:09 --- quit: gravicappa (Ping timeout: 276 seconds) 14:06:35 --- quit: Keshl_ (Quit: Konversation terminated!) 14:31:37 --- quit: xek (Ping timeout: 265 seconds) 14:46:50 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 15:16:54 --- quit: inode (Quit: ) 15:54:14 --- join: dave0 (~davezero@069.d.003.ncl.iprimus.net.au) joined #forth 16:03:31 --- join: learning (~learning@47.138.187.107) joined #forth 17:02:25 --- join: rdrop-exit (~markwilli@112.201.170.86) joined #forth 17:51:38 --- quit: ryke (Ping timeout: 245 seconds) 18:38:40 --- quit: learning (Remote host closed the connection) 18:44:22 --- quit: dddddd (Remote host closed the connection) 18:46:01 --- quit: dave0 (Quit: dave's not here) 18:50:25 --- join: tabemann (~tabemann@2600:1700:7990:24e0:9873:fa2b:cbf4:f93c) joined #forth 19:11:29 --- join: iyzsong (~iyzsong@fsf/member/iyzsong) joined #forth 19:19:25 --- quit: iyzsong (Quit: ZNC 1.7.4 - https://znc.in) 19:27:35 --- quit: jedb (Remote host closed the connection) 19:27:52 --- join: jedb (~jedb@185.128.24.51) joined #forth 20:05:34 --- join: tpbsd (~Terry@2001:44b8:314b:a800::10) joined #forth 20:05:34 --- quit: tpbsd (Changing host) 20:05:34 --- join: tpbsd (~Terry@mecrisp/staff/tp) joined #forth 20:05:34 --- quit: tp (Read error: Connection reset by peer) 20:42:22 --- nick: tpbsd -> tp 20:58:34 --- join: iyzsong (~iyzsong@fsf/member/iyzsong) joined #forth 21:26:44 --- quit: kori (Quit: WeeChat 2.6) 21:36:57 --- quit: iyzsong (Ping timeout: 246 seconds) 21:42:22 --- join: gravicappa (~gravicapp@h109-187-209-116.dyn.bashtel.ru) joined #forth 21:53:25 --- join: iyzsong (~iyzsong@fsf/member/iyzsong) joined #forth 22:50:11 --- quit: jedb (Read error: Connection reset by peer) 22:53:20 --- join: jedb (~jedb@185.128.24.51) joined #forth 23:13:55 --- join: nullnullnull (~nullnulln@31.154.190.34) joined #forth 23:27:23 --- quit: KipIngram (Ping timeout: 246 seconds) 23:52:21 c[] 23:52:44 g'day Zen Forth Master 23:53:03 Hi Master Technician! :) 23:53:50 I just had a nice free lunch for fixing a incredibly complex LED torch about 10 years old 23:54:14 cool 23:54:16 it has 3 'super caps' in it and is supposed to run for 4 hrs continuously 23:54:38 the caps are about the size of 'D' cells 23:55:06 so quite huge, but very light 23:55:12 --- quit: jedb (Read error: Connection reset by peer) 23:55:20 and the charger was also very complex 23:55:37 it retailed for about $180 USD 10 years ago 23:55:58 I carry a tiny USB-rechargeable "torch" on my keychain :) 23:56:35 it was beautiful made, solid as and I couldnt see any problems, so I just resoldered all the main solder joints and it worked :) 23:56:44 yeah, theyre very handy 23:57:30 I've never seen a more complex led torch, had a MCU in the charger and torch, seperate charge controllers for eash sipercap 23:57:36 supercap 23:57:44 I want to get one with a built-in movie camera, starts filming when you turn the torch on 23:58:05 clip it under your M14 barrel ? 23:58:29 For when I walk the dogs at night 23:58:58 they probably already exist 23:59:10 they do, but they're pricey 23:59:13 if not, design one and make your 2nd million # ? 23:59:22 yeah would be 23:59:40 They take a micro-SD card 23:59:41 and cheap ones from china wouldnt last long, have terrible resolution etc 23:59:59 --- log: ended forth/19.09.29