2022-06-01 00:17:39 <lilo_booter > KipIngram: i think you would probably be safest doing it by way of a live distro, yeah - you can't make modifications to mounted partitions afaik, but even if you could, i don't think i'd try it :) - gparted or fdisk should be fine though
2022-06-01 02:00:32 <dave0       > should    `1 2 3 depth pick .`    give `1` ie. the end of the stack? on gforth it goes one past the end (and doesn't check for out of bounds)
2022-06-01 02:03:05 <dave0       > seems to me `depth pick` and `depth roll` would be more useful if it grabbed the last value
2022-06-01 02:07:02 <lilo_booter > depth 1- pick would be what i'd expect for that tbh
2022-06-01 02:09:38 <lilo_booter > if you consider dup being 0 pick and over being 1 pick, then you should see that depth 1- would do the right thing for any number of items on the stack
2022-06-01 02:13:40 <dave0       > hmm yeah if there were three things on the stack... depth would be 3 and pick would be 0 to 2
2022-06-01 02:13:48 <lilo_booter > yup
2022-06-01 02:13:53 <dave0       > that's fair
2022-06-01 02:13:58 <dave0       > cool thanks
2022-06-01 02:14:01 <lilo_booter > np
2022-06-01 02:20:29 <dave0       > cool    depth 0 ?DO i pick . LOOP    prints the data stack (in reverse ;-) with how depth and pick works
2022-06-01 09:27:24 <KipIngram   > I agree with those conclusions (re depth pick)
2022-06-01 09:28:34 <KipIngram   > I don't have pick and haven't written depth yet.  I've tried to write this one writing just the words I need to make further progress (except for that fleet of Python generated ones).
2022-06-01 09:28:44 <KipIngram   > Haven't needed depth yet.
2022-06-01 10:21:56 <lagash      > This hit Lobste.rs, looks cool https://gitlab.cs.washington.edu/fidelp/frustration
2022-06-01 10:22:52 <thrig       > rust compiles never resulted in a cool laptop
2022-06-01 10:32:50 <thrig       > hella long time -> bizzaro compile error -> uninstalled rust
2022-06-01 13:46:11 <siraben     > lagash: I like the use of hygienic macros!
2022-06-01 13:48:29 <siraben     > last year I wrote a formal (small-step) operational semantics for a subset of Forth https://gist.github.com/siraben/4361eca01cb0395cfa3c993e0dd380f3 and used the coq notation system to make it possible to write forth directly
2022-06-01 13:48:48 <siraben     > `Definition down_to : com := <{ begin dup O= not while dec repeat }>.`, `<{` and `}>` are tokens that denote the start and end of a forth fragment
2022-06-01 13:49:16 <siraben     > then I can state and prove that the `down_to` program always leaves the top of stack with the number 0