00:00:00 --- log: started forth/20.04.22
00:24:26 --- join: jsoft joined #forth
00:26:25 --- join: mtsd joined #forth
00:48:11 --- join: xek joined #forth
01:25:33 --- quit: nonlinear (Ping timeout: 260 seconds)
01:30:26 --- join: nonlinear joined #forth
01:39:02 --- quit: WickedShell (Remote host closed the connection)
03:27:55 --- join: TCZ joined #forth
03:33:54 --- join: iyzsong joined #forth
03:41:34 --- join: rdrop-exit joined #forth
04:15:36 --- join: merkc0 joined #forth
04:15:59 <merkc0> : gen-shc CREATE
04:15:59 <merkc0>    5 0 DO  1 . LOOP
04:15:59 <merkc0>   DOES> @ ;
04:15:59 <merkc0> gen-shc myc
04:16:11 <merkc0>          ^ 0xC0000005L ACCESS_VIOLATION
04:16:34 <merkc0> why can't I use DO LOOP after CREATE ?
04:23:34 <rdrop-exit> shouldn't, which Forth?
04:24:04 --- join: dddddd joined #forth
04:25:18 <merkc0> you're right, it works when I isolate it; I have some other code above that messes things up
04:25:33 <rdrop-exit> ok :)
04:25:36 <merkc0> thanks
04:25:53 <rdrop-exit> no problem
04:30:55 <merkc0> BYE
04:30:55 <merkc0> BYE
04:31:02 * merkc0 wrong window
04:31:08 <rdrop-exit> :)
04:38:34 <merkc0> an on implementation without FORGET is it possible to redefine a word at the same address ? (without making a new entry in the dictionary )
04:40:41 <merkc0> given that the new definition is the same size as the old definition
04:40:51 <rdrop-exit> in theory, but you'd need detailed knowledge of the internals of the Forth, and even then it may not be practical
04:44:12 <rdrop-exit> on some simple Forths it would not be hard
04:44:18 <merkc0> I have a word that contains fixed assembly code and some data which I want to update from user input 
04:44:55 <merkc0> I am not sure how to update the data in that asm code, in an elegant way
04:45:37 <rdrop-exit> that type of patching should be easy
04:47:28 <rdrop-exit> while you're assembling your word, save the patch address somewhere
04:49:25 <merkc0> ok I'll give this approach a try
04:52:08 <rdrop-exit> if you know the address that you want to patch, just make a constant out of it, and store your patching data at that address
04:53:08 <rdrop-exit> using c! 16! 32! or whatever depending on the width of the data
04:54:24 <rdrop-exit> (your Forth may have other names for 16! etc, eg. w! )
04:57:30 <merkc0> got it
04:58:09 <rdrop-exit> If you're running on an OS, or on a heavily pipelined CPU, self-modifying code may be problematic
04:58:10 <merkc0> is it not possible to change 1) backup HERE 2) HERE to point to the desired address and do the word compilation 3) revert to the old backup ?
05:00:06 <rdrop-exit> you could if your dictionary is combined code & data, but backing up HERE seems more trouble then it's worth if you're just patching a few bytes
05:00:35 <merkc0> 2 bytes and 2 unicode strings 
05:02:15 <rdrop-exit> and you need to be careful not to cause an error while you're temporarily messing with HERE, i.e. DP
05:02:34 <rdrop-exit> I would just have a constant of the patch address
05:03:25 <rdrop-exit> is this a desktop system?
05:03:42 <rdrop-exit> (I ask because you mentioned Unicode)
05:05:00 <rdrop-exit> if it is a desktop system, than self-modifying code is probably not worth messing with
05:05:49 <merkc0> yes it's desktop
05:06:25 <rdrop-exit> just have the assembly code get the data it needs from a variable that you can change based on user input
05:07:34 <merkc0> I'm injecting this assembly into another process , so I have to inject the data as well 
05:09:06 <rdrop-exit> ah, then another system/process is actually going to run the machine code you're generating, then that's less problematic
05:09:47 <merkc0> yes it's another system that's running that code
05:10:13 <merkc0> simple dumb asm code that won't call any forth words
05:10:34 <rdrop-exit> like a virus?
05:10:57 <merkc0> like a "good virus", it adds functionality to a software
05:11:13 <merkc0> which is not extensible by other means
05:11:21 <rdrop-exit> cool
05:13:43 <rdrop-exit> if the machine code is intended for a target, then you're situation is much simpler to deal with
05:13:48 <rdrop-exit> overall
05:14:54 <rdrop-exit> you can lay down machine code to a buffer, rather than making it part of your dictionary
05:15:17 <merkc0> how to use C,   etc, to lay it down to a buffer ?
05:15:49 <merkc0> w,    16, 32, 
05:16:42 <merkc0> CREATE buffer         then I add the stuff    w, w, w,      
05:17:16 <merkc0> then how to lay down again, the same stuff (maybe with some data changed) , at the same buffer address
05:17:28 <rdrop-exit> you can write variant comma words for the target, maybe tb, t16, t32, etc...
05:18:05 <rdrop-exit> you reset the pointer that's tracking your usage of that buffer
05:18:32 <rdrop-exit> variable tp \ target pointer
05:19:08 <rdrop-exit> create target 128 allot
05:19:26 <rdrop-exit> : tp0 ( -- ) target tp ! ;
05:19:59 <tp> nono please dont target me!
05:20:10 <merkc0> lolz
05:20:34 <rdrop-exit> tp0 resets your target pointer back to the beginning of the target buffer when you want to reuse it
05:20:57 <rdrop-exit> :))
05:22:24 <rdrop-exit> then you make a bunch of comma words that lay down whatever you want into that buffer
05:22:53 <rdrop-exit> dinner is served, gotta go, stay healthy
05:22:59 --- quit: rdrop-exit (Quit: Lost terminal)
05:36:38 --- join: jedb_ joined #forth
05:37:09 --- quit: jedb (Ping timeout: 256 seconds)
05:45:05 --- join: mtsd_ joined #forth
05:46:56 --- quit: mtsd (Ping timeout: 240 seconds)
05:48:58 --- quit: mtsd_ (Client Quit)
06:05:18 <veltas> tp: I read some of that "Extraordinary Popular Delusions..." book, was interesting, but I feel like I'm getting someone's personal slant instead of a balanced look at the history
06:05:51 <veltas> But it got me interested in stuff I'd not heard of before so I guess I can always research it myself if I really care
06:23:57 --- quit: merkc0 (Quit: Leaving)
06:27:12 --- quit: TCZ (Quit: Leaving)
06:30:43 --- join: merkc0 joined #forth
06:47:05 --- quit: gravicappa (Ping timeout: 260 seconds)
06:51:00 --- quit: Zarutian_HTC (Ping timeout: 264 seconds)
06:52:01 --- join: TCZ joined #forth
06:55:40 --- join: gravicappa joined #forth
07:26:54 <merkc0> BYE
07:26:54 <merkc0> BYE
07:27:12 * merkc0 wonrg wnd
07:29:16 --- quit: TCZ (Quit: Leaving)
07:29:34 --- join: TCZ joined #forth
07:30:21 --- quit: TCZ (Remote host closed the connection)
07:30:41 --- join: TCZ joined #forth
07:47:06 --- quit: cantstanya (Ping timeout: 240 seconds)
08:06:32 --- join: cantstanya joined #forth
08:07:49 --- nick: jedb_ -> jedb
08:18:26 --- quit: TCZ (Quit: Leaving)
08:18:49 --- join: TCZ joined #forth
08:21:13 --- join: Zarutian_HTC joined #forth
08:30:59 --- quit: TCZ (Quit: Leaving)
08:37:34 <veltas> merkc0: it's too late
08:37:44 <veltas> We already know you use caps
08:37:52 <merkc0> :)
08:40:26 <merkc0> BYE
08:40:26 <merkc0> BYE
08:40:53 <veltas> ok
08:40:55 <merkc0> I'm using a keyboard macro, to automatically switch and trigger compilation
08:41:19 <merkc0> switch window.. and when xchat happens to be the 2nd window, you get to see BYE BYE
08:53:49 <merkc0> BYE
08:53:49 <merkc0> BYE
09:04:33 --- quit: dave0 (Quit: dave's not here)
09:10:17 <dzho> so, one sees forths written *for* FPGA's but are there Forth high-level synthesis (HLS) compilers?
09:10:20 <dzho> http://blog.llvm.org/2020/04/the-new-clang-extint-feature-provides.html
09:12:23 --- join: X-Scale` joined #forth
09:12:32 <veltas> Didn't Chuck Moore write something like that?
09:13:02 <veltas> Or might have been different kind of tool, since his was for designing silicon I think .. ?
09:14:05 <veltas> It's not fair for us to put all this weight on Chuck Moore but the moore we ask of him the moore he does
09:14:19 <dzho> heh
09:14:25 --- quit: X-Scale (Ping timeout: 258 seconds)
09:14:25 --- nick: X-Scale` -> X-Scale
09:14:36 <veltas> https://colorforth.github.io/vlsi.html
09:20:44 <veltas> So they want to add specific bit width integers to C....... I feel like they are missing that this feature is already in C. Just not how they want it apparantly.
09:21:14 <veltas> Does their proposal solve a problem other than making it nicer for LLVM?
09:25:04 --- join: merkc1 joined #forth
09:28:48 --- quit: merkc0 (Ping timeout: 264 seconds)
11:48:34 --- join: cox joined #forth
11:48:39 --- nick: cox -> mark4
11:49:00 <mark4> anyone here have word that can reverse the order of N1 items on the stack? :)
11:49:54 <mark4> ( x0 x1 x2 n1 --- x2 x1 x0 ) for any value of n1 :) 
11:50:24 <mark4> call it ><  the  2 >< would be a swap :P
11:50:43 <mark4> : swap ( n1 n2 --- n2 n1 ) 2 >< ;  
11:51:09 <mark4> and a swap rot could be done with 3 ><
11:52:17 --- quit: merkc1 (Ping timeout: 256 seconds)
11:53:06 --- quit: gravicappa (Ping timeout: 258 seconds)
12:13:50 <tp> SpaceX is targeting Wednesday, April 22 at 3:30 p.m. EDT, or 19:30 p.m. UTC, for its seventh launch of Starlink satellites
12:35:40 --- quit: Croran (Ping timeout: 246 seconds)
12:40:49 --- join: [1]MrMobius joined #forth
12:40:49 --- quit: MrMobius (Ping timeout: 260 seconds)
12:41:05 --- nick: [1]MrMobius -> MrMobius
12:42:33 --- join: WickedShell joined #forth
12:46:21 --- join: Croran joined #forth
13:02:03 --- quit: jsoft (Ping timeout: 256 seconds)
13:34:55 --- quit: xek (Ping timeout: 250 seconds)
14:11:13 --- join: TCZ joined #forth
14:21:56 <veltas> mark4: : >< 1 ?DO I ROLL LOOP ;
14:23:44 <veltas> If you want to support n1 < 1 then you want an IF as well
14:37:13 <mark4> im not sure that i roll would do it
14:37:25 <mark4> i think it would be like doing rot rot rot
14:37:41 <mark4> where really in this case you would need swap rote
14:38:00 <mark4> oh wait. maybe it would work :)
14:38:11 <mark4> i dont think i ever implemented roll :)
14:38:19 <mark4> pick yes but im not sure roll
14:38:27 <mark4> it was just an academic question anyway :)
14:40:59 <mark4> also, not sure we met before :)
14:41:08 <mark4> hi :)
14:44:41 <TCZ> "THEN THEN THEN THEN DROP" should be song lyrics
14:50:53 <crc> mark4: not standard, but:
14:51:14 <crc> :><  (...n-...)  &Heap [ here [ dup , &, times ] dip [ ] a:for-each ] v:preserve ;
14:56:30 <crc> see gopher://forth.works/0/share/105674ac5822baa8ab6d8f6178152d5c or http://forth.works/share/105674ac5822baa8ab6d8f6178152d5c for brief documentation on the words used in this
14:59:49 --- quit: mark4 (Remote host closed the connection)
15:00:10 --- join: mark4 joined #forth
15:20:21 --- join: dave0 joined #forth
15:30:22 <veltas> mark4: Hi
15:31:14 <TCZ> "oh hi mark"
15:34:00 <mark4> hi :)
15:34:21 <mark4> tcz is very similar to tcn, you arent tcn in disguise are you? :)
15:34:56 <mark4> currently working for cox communications automotive division and the project is usig the "awesome" pic32 (puke)
15:35:01 <mark4> so im writing a pic32 assembler lol
15:35:13 <mark4> so i can write a forth just for the "fun" :)
15:36:06 <TCZ> https://www.youtube.com/watch?v=Jv3MhjSmR3c
15:36:17 <TCZ> no i dont know what is tcn :)
15:39:50 <veltas> A PIC32 sounds fun to be honest, more powerful than what I'm working with atm
15:39:58 <veltas> mark4: Why write a forth though?
15:42:12 <mark4> i have written manu, x86 arm, thumb2, 8051, avr :)
15:42:31 <mark4> pic32 is ok, the damned microchip development tools are utter garbage
15:42:37 <mark4> speciallhy their IDC4
15:43:24 <mark4> im writing data out i2c to an external nvm then reading it back in and comparing it to what was written, the test is passing but if i view the contents of the buffers using the freeking IDE they LOOK wrong
15:43:27 <mark4> utterly fscking useless
15:43:49 <mark4> wish they had picked armv7 tho
15:44:21 <veltas> Are they making a lot of these?
15:44:34 <veltas> PIC32 is cheaper I'm assuming
15:45:10 <mark4> pretty much everything microchip is garbage imho :)
15:45:34 <mark4> with pic16 and pic24 you cannot even guarantee the debugger will stop on your breakpoint
15:45:49 <mark4> you have to use skid buckets, place 2 nops after the opcode you want to stop on
15:45:57 <mark4> so the cpu can come to a screeching halt
15:45:59 <veltas> tp: Does 'microchip' mean something other than what I think it does?
15:46:02 <mark4> eventually
15:46:15 <mark4> microchip is the maker of the PIC processors
15:46:20 <mark4> they also own AVR now
15:46:26 <mark4> unfortunately.
15:46:32 <mark4> avr is awesome, PIC is garbage
15:46:37 <veltas> Oh right
15:47:07 <veltas> 'microchip' is kind of what people used to call what is probably called a 'chip' now
15:47:13 <veltas> that's confusing
15:47:26 <mark4> thats why they picked that name, they make microchips
15:47:51 <mark4> brb, letting dog out a ssec
15:49:43 <veltas> That would be like Ford calling itself Car
15:50:09 <veltas> Or like me calling myself Glorified Coffee-In-Code-Out Machine
15:50:40 --- quit: TCZ (Quit: Leaving)
15:50:42 <mark4> PIC32 however was not designed by microchip, internally its MIPS
15:54:18 <veltas> Is that why you're writing a forth? Their dev tools suck?
16:06:29 <mark4> no, im doing it just for the fun of it
16:06:36 <mark4> we wont be using forth at work :)
16:10:06 <veltas> One day I'm sure I'll find an excuse to use forth at work
16:10:06 <mark4> im writing the mips assembler first, it will support mips 1, 2, 3 and 4
16:10:13 <mark4> where do you work?
16:10:32 <veltas> If I get proficient enough I might use forth for 'simple scripts'
16:10:50 <veltas> Not a good idea to put personal info like that under my name
16:11:20 <mark4> well if you are doing scripts then you are working in linux yes?
16:11:39 <veltas> We use Windows, Linux I will run a VM for
16:11:46 <mark4> aha
16:11:48 <veltas> Not my choice
16:12:00 <mark4> what forth do you use in the vm or dont you have one there hyet
16:12:01 <mark4> yet
16:12:13 <veltas> gforth probably
16:12:20 <mark4> ick
16:12:30 <veltas> It's not something I do right now
16:12:31 <mark4> not a fan of forths written in c
16:12:53 <veltas> I write my quick scripts in Lua atm
16:12:55 <mark4> as far as im concerned any forth that can not compile its own sources is deficient
16:13:06 <mark4> and in the case of a c based forth, is not even forth
16:14:30 <mark4> not a fan of lua either but its better than python :)
16:14:46 <mark4> wow's interface was coded in LUA by the guy that wrote SDL
16:15:13 <veltas> This is what they have to say https://www.complang.tuwien.ac.at/forth/gforth/Docs-html/Portability.html#Portability
16:15:27 <veltas> About writing it in C
16:15:46 <mark4> portability is a) a myth and b) pointless, it makes all portable code look like a cluster )$Y(! unmade bed
16:16:02 <mark4> give me a good design and a good implementation and porting is ***TRIVIAL***
16:16:09 * veltas shrugs
16:16:19 <mark4> taking care of all that visual clutter red tape is a horrendous mess
16:16:41 <veltas> I write 'portable' code for hosted and freestanding environments a lot, athough there is obviously a limit to the portability, with not too much clusteryness
16:17:29 <veltas> I think it all depends honestly
16:17:39 <mark4> it can be done, usually when people try to do it they end up making things way worse
16:17:52 <mark4> java is theoretically portable
16:17:55 <mark4> c is not
16:18:11 <mark4> which is why all those libraries need to have #ifdef xxx yyy or zzz all over the place
16:18:23 <mark4> cluster bleep
16:18:27 <mark4> gordian knot
16:18:35 <veltas> https://en.wikipedia.org/wiki/CP/M#Portability
16:18:55 <mark4> wikipedia, the oracle of all kowledge.... true and false :)
16:18:57 <mark4> lol
16:19:06 <veltas> I don't know about this 'pure' portability but my idea of portability is what CP/M used
16:19:19 <veltas> I was just using wikipedia for context, not to try to 'prove' anything
16:19:28 <mark4> i know
16:19:40 <mark4> and if you touched cpm you are an old fart like me
16:19:51 <mark4> i never liked z80 tho :)
16:21:52 <veltas> I've never used CP/M, I just know about software history
16:22:10 <mark4> aha
16:22:36 <veltas> What is your quick scripting language?
16:23:13 <veltas> Like if I asked you to do some simple mundane processing on a load of files, without using a shell script
16:23:59 <mark4> well i dont do bash, lua or python lol
16:25:07 <veltas> Because for simple mundane processing on a load of files I know I'd use find or bash, but I mean the general purpose language you choose to do quick and dirty stuff
17:03:58 <tp> mark4, youre a serious dude, dude :)
17:05:00 <tp> mark4, I'm a old dude also, I think we have spoken before as I just do embedded forth, Im a tech not a systems writer
17:06:18 <tp> veltas, Microchip it the company that makes "PIC" mcus, and PIC's are pretty old now. They also now own AVR which was a breakaway group of Microchip engineers initially I think
17:07:53 <veltas> This is why capital letters help
17:08:25 <veltas> tp: Have you watched Tiger King?
17:08:26 <tp> I think theyre a capital idea old chap
17:08:35 <tp> veltas, no
17:08:50 <veltas> capital
17:08:59 <mark4> :)
17:09:05 <mark4> im a heretic and know it :)
17:09:34 <mark4> tp no actually the AVR was developed by 2 uni sutdents in norwawy
17:09:37 <mark4> oslo?
17:09:49 <mark4> when they got out of uni they started the AVR corporation 
17:09:58 <mark4> avr is whats in arduino
17:10:07 <tp> mark4, I agree with everything you have said, tho I did use the PIC in a product I made in the late 90's, just a small run of a custom instrument
17:10:16 <mark4> Microchip has been trying for YEARS to buy tuenm
17:10:21 <mark4> err Atmel not AVR
17:10:29 <mark4> AVR is the chip, Atmel is who made it
17:11:26 <tp> mark4, oh ok, I know about the norway connection ... but I guess I'm confused about the breakaways
17:11:41 <tp> mark4, I know ATMEL all too well sadly
17:11:48 <tp> I hate the dam things
17:11:59 <mark4> which things? avr or microchip?
17:12:10 <mark4> atmel also made 8051s
17:12:11 <tp> AVR, mega16 and 32 mainly
17:12:30 <mark4> i like avrs, way better than PIC
17:12:40 <tp> apart from making a programmer for 8051's Ive never like them much either
17:12:47 <mark4> i wrote a very nice avr assembler too :)
17:13:00 <mark4> 8051 was the first assembler i ever wrote :)
17:13:16 <tp> I had to make 20 Mega32 units a day for about a year, too flakey for me
17:13:20 <mark4> the sources to that assembler are in the x4 repo too but there is a small bug i never fixed
17:13:36 <mark4> i like the 32u4
17:13:39 <tp> thats why Im not a AVR fan
17:13:42 <mark4> dream to code for
17:13:55 <mark4> anything PIC is horrible to develop for
17:14:24 <tp> I'm all stm32 and MSP430 now
17:14:25 <mark4> once you get above 8k of code space, any change in module A will have a random unexplainable affect in module b, so fixing b will affect c... ad infinitum
17:14:29 <tp> oh I agree there
17:14:43 <mark4> msp430 was developed by TI to do power metering
17:14:45 <tp> microchips support always sucked
17:15:01 <tp> I ranted and raved about that for decades
17:15:05 <mark4> lol
17:15:29 <mark4> if you like arm cores you should check out my T4 forth compiler
17:15:35 <mark4> thumb2 asm for linux arm 
17:15:51 <tp> Im happy with cortex-m and MSP430 now, I dont need to look any further
17:16:19 <tp> mark4, Im all into Mecrisp-Stellaris Forth for cortex-m and MSP430
17:16:49 <tp> mark4, this is me:https://mecrisp-stellaris-folkdoc.sourceforge.io/index.html 
17:16:54 <mark4> cortex-m IS thumb2 :)
17:17:01 <tp> and https://mecrisp-across-folkdoc.sourceforge.io/
17:17:23 <tp> mark4, no, not the variant I use, it's thumb1 only
17:17:31 <tp> cortex-m0 namely
17:18:02 <mark4> ewwww i think thumb1 is a poor design, in fect i think all arm instuction sets are over engineered and badly designed EXCEPT thumb2 lol
17:18:17 <tp> in any event, I'm a tech not a real programmer, which makes me a "USER"
17:18:33 <tp> mark4, software people have opinions like that :)
17:18:52 --- quit: WickedShell (Remote host closed the connection)
17:18:56 <tp> mark4, I couldnt care less about all that, I just use em to make stuff
17:19:05 <mark4> :)
17:19:16 <tp> mark4, as long as my tools are adequate, Im happy
17:19:46 <mark4> github.com/mark4th has both x4 and t4 compilers of mine
17:20:10 <mark4> i was working on a64 (arm 64) but got too much on my plate right now
17:20:17 <mark4> so im just keeping it simple
17:20:23 <mark4> pick that up later
17:20:28 <tp> yes I know, we have spoken about them before :)
17:22:51 <tp> I'm either a chip hosted Forth user (cortex-m) or a tethered Forth user (msp430)
17:23:16 <tp> if I do any assembly I'll do it with a tethered forth, lol
17:23:57 <mark4> well its a bit hard to fit both the forht kernel and all its headders AND an assembler on a hosted embedded forth lol
17:24:06 <mark4> thats only really viable with a tethered forth
17:24:24 <mark4> all creating words are on the host 
17:25:04 <tp> sure, but Mecrisp-Stellaris does have a forth-> machine code compiler on the chip of course
17:25:22 <tp> it just leases out the assembly stage, assemblers are for humans
17:26:03 <tp> I do remember the incredible joy of my first assembler, I was so sick of writing machine code on a hex keypad
17:28:52 --- join: WickedShell joined #forth
17:39:47 <mark4> lol
17:39:47 --- join: rdrop-exit joined #forth
17:51:03 --- join: merkc1 joined #forth
17:51:16 <rdrop-exit> (-_-)zzz c[] good morning Forth connoisseurs
17:52:15 <tp> morning Zen Forth Guru !
17:52:48 <rdrop-exit> hi Forth Master Tech (tm)
17:56:12 <tabemann> hey guys
17:56:23 <rdrop-exit> hi tabemann
17:56:47 --- quit: merkc1 (Ping timeout: 265 seconds)
17:56:48 <tp> hey tabemann 
17:57:28 <tabemann> tp: where's that script of yours which shows how to use screen from within a shell?
17:58:12 <tabemann> I know you sent it to me a while back
17:59:08 <tp> tabemann, I'll pastebin it
17:59:48 <tabemann> because I'm thinking what I could do is make a script to generate a full binary for a given platform
18:00:01 <tabemann> generating one for all platforms is not feasible
18:00:17 <tp> yeah
18:00:23 <tabemann> but now that I have codeload3.py doing them for one platform at a time should be within reach
18:00:46 <tabemann> and far less error-prone than what I had been doing manually
18:01:39 --- quit: mark4 (Read error: No route to host)
18:01:55 --- join: cox joined #forth
18:01:58 <tp> tabemann, is this the one ? http://dpaste.com/1S7TDV0
18:03:18 <tabemann> that might be it
18:03:53 <tp> tabemann or this one ? http://dpaste.com/1FGXRM4
18:04:20 <tp> tabemann, in either case, both those scripts are auto generated by other scripts :)
18:04:31 <tp> it's scripts all the way down!
18:05:06 <tabemann> heh
18:06:28 --- quit: boru (Ping timeout: 258 seconds)
18:07:40 <tabemann> stupid question
18:07:53 <tabemann> how do you tell screen to disconnect from the command line
18:08:07 <tp> actually all the questions around here are quite complex
18:08:08 <tabemann> because, let's say, I want to run codeload3.py again
18:08:41 <tp> the only way I know is to quit from screen
18:08:58 <tp> which I have on a hotkey, but I rarely use it
18:09:13 <tp>  :quit
18:09:44 <tabemann> lol - just figured that one out a sec ago
18:10:12 <tp> screen is very stubborn Ive found ;-)
18:40:28 <tabemann> question
18:41:11 <tabemann> how the fuck do I create a screen session that is connected to the serial port but not to the terminal emulator?
18:44:16 <tp> easy
18:46:27 <tabemann> and
18:46:30 <tp> sorry just buying some masks on like atm
18:46:34 <tp> online
18:49:37 <tp> tabemann, I only know how to remotely connect to a session first established by a terminal connection
18:49:54 <Zarutian_HTC> tp; 
18:50:04 <tp> Zarutian_HTC, :)
18:50:36 <Zarutian_HTC> tp: does cat come anywhere into the picture?
18:51:07 <tp> Zarutian_HTC, which picture ?
18:51:12 <rdrop-exit> cat pictures
18:51:22 <tp> meeow
18:51:37 <Zarutian_HTC> of getting a serial link to work with screen
18:52:09 <tp> Zarutian_HTC, no, no felines are involved there
18:52:37 <Zarutian_HTC> and I meant the command cat not felines
18:52:43 <tp> Zarutian_HTC, thats why screen is cool, it has inbuilt remote serial connection facility
18:53:20 <Zarutian_HTC> you jus give it the path to the serial device or?
18:53:21 <tp> Zarutian_HTC, unlike the japanese copy which has zero serial facilities
18:53:35 <rdrop-exit> just use Forth
18:54:55 <tp> Zarutian_HTC, here I send a command to a serial device      screen -p $PROJECT -X stuff "reset\n" 
18:55:19 <tp> $PROJECT is the name of the connection
18:57:16 <tp> Zarutian_HTC, here I upload a file to the serial connection, part one, save the file to a screen "register"     screen -p $PROJECT -X readreg x   myfile.forth     
18:58:04 <tp> part 2: 'paste the file to the terminal screen"        screen -p $PROJECT -X paste x
18:58:31 <tp> in this case the register is "x" and there are 26 registers, a - z
18:59:09 <Zarutian_HTC> how do you get that screen window/session up and going in the first place?
19:00:40 <tp> Zarutian_HTC, http://dpaste.com/2BM6W55
19:01:27 <tp> Zarutian_HTC, thats for a screen connection, 460800 baud, hardware handshaking etc
19:07:12 <Zarutian_HTC> simple as: screen <pathToSerialDevice> <bpsAndOtherSuchSettings>
19:07:41 <tp> yeah
19:08:02 <tp> in this case the script establishes a session using the directory name
19:08:35 <Zarutian_HTC> and does so in an xterm window
19:08:45 <tp> which means that for me I dont need any special config for that script as my projects are all the same name as the directory name
19:08:49 <tp> yes
19:09:12 <tp> it also provides some info in the top bar of the xterm
19:09:33 <tp> which I need as I may have more than one screen session open
19:09:34 <Zarutian_HTC> hmm handy to know how to do this then
19:09:39 <tp> :)
19:10:04 <tp> it took me about 3 years to get to that point after trying every terminal in existence
19:10:41 <tp> the alternative is to 1) write your own terminal, not for me, I'm a tech
19:10:46 <Zarutian_HTC> what if I need to pipe the output of that connection to another program?
19:10:57 <tp> 2) use unix utils that allow this kind of thing
19:11:20 <tp> you can use tee I imagine
19:11:33 <tp> but screen allows one sub program to be run as well
19:11:45 <tp> and thats the last line of my script
19:11:52 <Zarutian_HTC> ahh, tee it into a fifo, I see
19:12:04 <tp> error-bell.sh
19:12:52 <tp> PROJECT=`basename $PWD`
19:12:53 <tp> screen -p $PROJECT -X exec :sed -nr 's/.*compile-only.*|.*Create.*|.*found.*|.*flow.*|.*balanced.*|.*Redefine.*/\007\033[31;1;4mERR\033[0m/p'
19:13:25 <Zarutian_HTC> dings at you if these error occur I see
19:13:28 <tp> what that does is parse the incoming data to screen and look for error messages
19:13:31 <tp> yeah
19:13:51 <tp> but it also INSERTS a RED "ERR" message into the receive stream
19:14:00 <tp> which I also log
19:14:34 <tp> so when I hear a bell I can either scroll screen data up with the mouse or look in the log
19:14:52 <tp> in the former I'll see the big RED marker
19:15:02 <tp> in the latter I have to search for "ERR"
19:15:43 <tp> now I may be uploading 10kB of Forth source, and at 460800 baud, it's way to fast to see, so I need the bell
19:16:17 <tp> in fact if I didnt have the bell, I'd go back to C
19:16:41 <tp> but I DO have the bell, and C will never see my smiling face again ...
19:19:39 <Zarutian_HTC> myself would have just written an interfacer in tcl/tk giving me the option to stop the upload and also visualize telemetric data if needed
19:20:22 <tp> thats because youre a programmer
19:20:30 <tp> and you know tcl/tk
19:20:44 <tp> and you know how to cook polar bear
19:20:57 <tp> I dont know any of those things
19:21:34 <tp> but all considered, the bell is all I need
19:21:37 <Zarutian_HTC> programmer and electronics tech. I just find it easier to throw such together in tcltk than do bash and other unix utils
19:22:19 <tp> my first method was to hack Mecrisp-Stellaris source and make a error drop CTS, then the upload would freeze on the error
19:22:51 <tp> but maintaining a patch for that is a pain and I found doing it at the PC level was tons easier
19:23:03 <Zarutian_HTC> cook a polar bear? why would i want to do that? the poor creaters are contamination concentrators as they are the apex predator of that food web
19:23:33 <tp> as in coronabear virus ?
19:23:54 <Zarutian_HTC> lame!
19:24:06 <Zarutian_HTC> ;þ
19:25:48 --- join: jsoft joined #forth
19:25:54 <tp> Zarutian_HTC, learning tcl/tk is on my list
19:26:55 <Zarutian_HTC> it is rather friendly, you can try things and the error messages are descriptive
19:27:59 <tp> i have started learning and working thru a tutorial, seems ok and I love the widgets
19:28:19 <tp> I was writing GTK2-Perl before that and had no problem
19:36:53 --- join: boru joined #forth
19:37:01 <tabemann> back
19:39:33 <tabemann> got my build script working, but with the downside that there cannot be any other screen sessions in the system
19:40:10 <tp> how come ?
19:40:23 <tp> I usually have 2 -3 running at the same time
19:40:35 <tabemann> because it doesn't use -p
19:41:51 <tp> ?
19:42:24 <tabemann> well -p tells it which session to use
19:43:56 --- quit: dave0 (Quit: dave's not here)
19:44:03 <tp> oh yeah <doh>
19:44:52 <tabemann> okay, I'm falling asleep, so g'night
19:45:59 <tp> g'night tabemann 
19:51:00 <rdrop-exit> back
19:51:24 <tp> welcome back! 
19:51:43 <rdrop-exit> thanks c[]
20:28:44 --- quit: jsoft (Ping timeout: 256 seconds)
20:35:19 --- join: reepca joined #forth
20:35:40 --- join: jsoft joined #forth
20:48:26 --- quit: cox (Quit: Leaving)
21:05:52 --- quit: Keshl (Read error: Connection reset by peer)
21:06:35 --- join: Keshl joined #forth
21:13:57 --- quit: Keshl (Read error: Connection reset by peer)
21:14:02 --- join: Keshl_ joined #forth
21:16:09 <rdrop-exit> I'm thinking of renaming my shift-or ops, to something more visual, anyone want to give me feedback?
21:17:11 <rdrop-exit> _| ( x1 x2 # -- x2<<#|x1 )
21:17:18 <rdrop-exit> |_ ( x1 x2 # -- x1<<#|x2 )
21:18:48 <rdrop-exit> the reason I want them more visual is I keep forgetting which is which
21:22:39 <rdrop-exit> (the old names are shorx \shorx )
21:23:22 <tp> lshift1 and lshift2 ?
21:23:36 <tp> or a picture of a cat  and dog ?
21:24:01 <rdrop-exit> brb phone call
21:30:40 <rdrop-exit> back, the underscore is meant to show me where x2 ends up
21:33:29 <MrMobius> you could go the APL route
21:33:44 --- join: merkc1 joined #forth
21:35:23 --- quit: rdrop-exit (Ping timeout: 256 seconds)
21:38:37 --- join: rdrop-exit joined #forth
21:38:57 <rdrop-exit> sorry lost my connection, some of my posts got lost:
21:39:17 <rdrop-exit> $ 123 $ 45 8 |_  gives $ 12345
21:39:18 <rdrop-exit> $ 45 $ 123 8 _| gives $ 12345
21:39:40 <rdrop-exit> oops, wife summoning me for lunch
21:39:58 --- nick: Keshl_ -> Keshl
21:39:58 <rdrop-exit> catch you in a bit, stay healthy
21:40:20 --- quit: rdrop-exit (Client Quit)
21:49:07 --- quit: Croran (Remote host closed the connection)
22:00:27 --- quit: dddddd (Ping timeout: 256 seconds)
22:24:02 --- join: gravicappa joined #forth
23:28:55 --- join: mtsd joined #forth
23:59:59 --- log: ended forth/20.04.22