00:00:00 --- log: started forth/20.06.26 00:25:35 --- quit: iyzsong (Quit: ZNC 1.7.5 - https://znc.in) 00:39:58 --- join: iyzsong joined #forth 00:51:03 --- quit: dys (Ping timeout: 265 seconds) 01:01:42 --- join: muzgo joined #forth 01:11:47 --- join: reepca` joined #forth 01:12:01 --- quit: reepca (Read error: Connection reset by peer) 02:11:12 --- join: xek joined #forth 02:30:00 --- quit: dddddd (Ping timeout: 258 seconds) 02:53:20 --- join: dys joined #forth 03:52:57 --- join: TCZ joined #forth 04:17:34 --- quit: Keshl_ (Quit: Konversation terminated!) 04:18:03 --- join: Keshl joined #forth 04:18:09 --- nick: Keshl -> Keshi 04:18:18 --- nick: Keshi -> Keshl 04:28:57 --- quit: TCZ (Quit: Leaving) 04:34:33 --- join: TCZ joined #forth 04:45:54 --- quit: TCZ (Quit: Leaving) 04:48:57 --- join: jedb_ joined #forth 04:52:10 --- quit: jedb (Ping timeout: 256 seconds) 05:26:53 --- quit: dave0 (Quit: dave's not here) 05:35:29 --- quit: dys (Ping timeout: 260 seconds) 06:03:29 --- join: dddddd joined #forth 06:04:02 --- join: clemens3 joined #forth 06:04:46 hi, what is the most popular forth on linux, is it gforth? 06:18:28 gforth 06:28:40 --- join: deesix_ joined #forth 06:28:56 --- join: dddddd_ joined #forth 06:31:04 --- join: dddddd__ joined #forth 06:31:07 --- quit: deesix (Ping timeout: 258 seconds) 06:31:48 --- quit: dddddd (Ping timeout: 260 seconds) 06:31:56 --- nick: dddddd__ -> dddddd 06:33:59 --- quit: dddddd_ (Ping timeout: 246 seconds) 06:34:11 --- quit: deesix_ (Ping timeout: 264 seconds) 06:36:56 --- quit: dddddd (Ping timeout: 256 seconds) 06:39:36 --- join: dddddd joined #forth 06:47:55 --- join: deesix joined #forth 06:52:15 crest: thanks.. does gforth kinda need gforth to compile itself? 06:52:37 that would be .. kinda.. why not bootstrap instead.. 06:53:29 seems that was a short gforth journey 06:56:31 clemens3: iirc it compiles a minimal forth system and uses it to bootstrap 06:57:03 hope so, just it doesn't tell me yet how.. 06:57:19 --- join: dys joined #forth 06:57:20 ah, it does 06:57:25 need swig and the -forth 06:57:39 well, well, hope is up 06:57:47 clemens3: most linux distros should contain a ready to use gforth package 06:58:24 well, mine doesn't 07:00:00 but swig sounds fair 07:02:45 interesting 07:03:22 the thing I always find so ironic is when someone makes a new Forth because C is horrible then proceed to implement it in C 07:03:41 I always wondered why those people don't use another Forth to create their Forth 07:04:44 (save-forth-and-die) 07:05:00 I suspect it's something to do with the pervasiveness of register machines, and them not wanting to write swathes of assembly. Besides that, Forth compilers are comparably easy to write, and it's more fun, I guess. At least, ime. 07:06:58 clemens3: because they use C as portable assembly 07:10:26 well, if forth doesn't like c, fine, just base it on assembler for a minimal forth etc. 07:11:06 or don't support linux or unix 07:14:45 seems my swig doesn't offer --with-forth.. 07:15:31 so seems i also have to write my own forth.. 07:15:53 always 07:17:38 --- join: TCZ joined #forth 07:44:15 --- quit: X-Scale (Ping timeout: 240 seconds) 07:59:41 --- quit: jedb_ (Remote host closed the connection) 08:00:17 --- join: jedb joined #forth 08:01:44 --- quit: TCZ (Quit: Leaving) 08:03:12 --- quit: jedb (Remote host closed the connection) 08:06:41 --- join: jedb joined #forth 08:08:03 --- join: X-Scale joined #forth 08:28:28 --- quit: Croran (Ping timeout: 260 seconds) 08:45:07 --- quit: jedb (Remote host closed the connection) 08:46:32 --- join: jedb joined #forth 08:47:07 --- quit: jedb (Remote host closed the connection) 08:47:26 --- join: jedb joined #forth 09:00:12 --- quit: xek (Ping timeout: 260 seconds) 09:31:27 --- join: TCZ joined #forth 09:48:09 --- nick: Zarutian_HTC1 -> Zarutian_HTC 09:51:02 --- quit: jedb (Ping timeout: 246 seconds) 10:01:43 --- quit: Zarutian_HTC (Quit: Bye) 10:23:47 --- quit: TCZ (Quit: Leaving) 10:39:45 --- quit: dys (Ping timeout: 244 seconds) 10:53:16 --- quit: clemens3 (Quit: WeeChat 2.7) 11:07:32 --- join: dys joined #forth 11:40:52 --- quit: jsoft (Ping timeout: 260 seconds) 13:31:24 --- join: Zarutian_HTC joined #forth 14:20:15 --- quit: reepca` (Ping timeout: 240 seconds) 14:26:17 --- join: reepca joined #forth 14:30:06 --- join: crab1 joined #forth 14:30:18 What's up #forth 14:34:47 --- quit: gravicappa (Ping timeout: 264 seconds) 14:40:30 tabemann: did you do anything to implement ack/nak in swdcom for zeptoforth? 15:41:02 --- quit: crab1 (Quit: Connection closed) 16:07:02 --- join: jsoft joined #forth 16:34:13 --- quit: cantstanya (Remote host closed the connection) 16:37:00 --- join: cantstanya joined #forth 17:16:48 --- join: TCZ joined #forth 17:38:12 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 17:38:26 --- join: Zarutian_HTC joined #forth 17:47:40 --- quit: TCZ (Quit: Leaving) 18:03:32 --- join: dave0 joined #forth 18:15:26 --- join: jedb_ joined #forth 18:30:21 tabemann, tp: i added file uploads to swdcom 18:31:04 i used ascii control chars to allow uploads to be canceled by the target mcu 18:31:43 that enables the forth system to abort transfers and ignore the partial transfer 18:31:55 back 18:32:11 those two words are enough: 18:32:12 : cancel ( -- ) $18 emit begin key $19 = until ; 18:32:13 : require ( -- ) token find drop if cancel then ; 18:32:26 use NAK for canceling 18:32:29 to allow files to begin with require my-word 18:32:37 nak is used for error handling 18:33:11 i patched the Fehler_Quit and Fehler_Quit_n macros to embedd NAK in all error messages 18:33:28 zeptoforth already has NAK in all error messages 18:33:37 which does something else 18:33:41 this isn't an error 18:33:51 it uses ACK to indicate readiness for input 18:34:01 but a polite way for the microcontroller to tell the host that the file is already loaded 18:34:12 ich verstehe es 18:34:27 my "protocol" is fairly simple 18:34:59 i begin each file upload by injecting a little bit of forth code that emits an ascii file seperator 18:35:17 this is required to reset the line counter on the receiving end 18:36:00 and i can use literal control char because the mecrisp accept word would remove it from the input 18:36:31 which in neatly removes it from the echo *sigh* 18:37:07 yeah, zeptoforth does the same thing - control characters it does not recognize it removes from the input buffer and does not echo 18:37:37 which prevents the host from using them to sync on 18:38:14 took a me way too long to look into the code and find my way from quit -> query -> accept 18:38:21 theres a reason why control characters need to be stripped 18:38:28 which one? 18:38:45 because otherwise, if you pressed up, the cursor would go up, which is really confusing to the user 18:39:51 wouldn't it be enough to ignore escape? 18:40:03 well that's what it does 18:40:14 this way it just outputs a bit of garbage 18:40:17 escape is just one of 32 chontrol characters 18:40:35 okay you don't want to echo the rest of the escape sequence 18:41:09 you can't strip out the rest of the escape sequence because it consists of printable characters 18:41:17 --- join: boru` joined #forth 18:41:20 --- quit: boru (Disconnected by services) 18:41:23 --- nick: boru` -> boru 18:41:51 so you didn't attempt to detect all common escape sequences^ ^ 18:41:53 * tabemann wonders what's up with tp, since he's seemed to've vanished; same with rdrop-exit 18:42:07 no I didn't 18:42:13 tabemann: he was active in #mecrisp the last few days 18:42:39 there's too many and they're too complex to catch'em all; better to not bother 18:42:46 i agree 18:42:53 so why not just ignore escape 18:43:12 and echo unknown escape sequences 18:43:25 but treat them as spaces otherwise 18:43:36 or just ignore them completly 18:43:37 because other characters may have other weird effects if echoed 18:43:53 like if you echoed XON or XOFF 18:44:03 in that case there is no better solution than injecting code 18:44:26 e.g. "\n$xx emit\n" 18:44:34 to send a control char 18:44:41 that works 18:45:33 oh and i found a simple solution to download hexdumps through swdcom 18:45:48 it just disconnects if it reads a ascii end of transmission 18:47:02 I could add that to ihex 18:47:27 $4 emit 18:47:46 the next steps are boring 18:47:57 document the code, clean it up a little 18:48:37 and improve the upload handling 18:51:48 --- join: karswell joined #forth 19:31:37 --- quit: reepca (Read error: Connection reset by peer) 19:31:51 --- join: reepca joined #forth 19:54:36 --- quit: jedb_ (Remote host closed the connection) 19:55:23 --- join: jedb_ joined #forth 20:10:18 --- quit: reepca (Ping timeout: 258 seconds) 20:12:38 --- quit: kamid (Ping timeout: 246 seconds) 20:19:38 --- join: karswell_ joined #forth 20:19:38 --- quit: karswell (Remote host closed the connection) 21:11:52 --- quit: jsoft (Ping timeout: 256 seconds) 21:36:39 --- quit: Zarutian_HTC (Quit: Bye) 21:36:51 --- join: Zarutian_HTC joined #forth 22:16:53 --- quit: karswell_ (Ping timeout: 246 seconds) 22:24:47 --- quit: jedb_ (Read error: Connection reset by peer) 22:54:24 --- quit: _whitelogger (Remote host closed the connection) 22:57:26 --- join: _whitelogger joined #forth 23:04:05 --- quit: dddddd (Ping timeout: 265 seconds) 23:18:05 --- join: gravicappa joined #forth 23:20:07 --- join: jedb joined #forth 23:21:58 --- join: jedb_ joined #forth 23:24:28 --- quit: jedb (Ping timeout: 260 seconds) 23:26:40 --- join: jsoft joined #forth 23:59:59 --- log: ended forth/20.06.26