2025-04-09 00:03:51 <cleobuline  > i will do RESUME WORD tu resume a thread
2025-04-09 15:28:27 <zozo        > helo
2025-04-09 17:46:34 <ohnoitsnoah > hey! anyone here?
2025-04-09 17:46:47 <thrig       > nope
2025-04-09 17:46:53 <ohnoitsnoah > shame
2025-04-09 17:47:01 <thrig       > yeah I know
2025-04-09 17:57:56 <lispmacs[work]> I'm not here
2025-04-09 18:51:13 <veltas      > thrig: Okay I like vim a bit less after having to check its source recently
2025-04-09 18:51:53 <veltas      > Looking for a bug, although it wasn't the culprit
2025-04-09 19:01:27 <xentrac     > heh
2025-04-09 19:01:42 <xentrac     > you prefer your source code files to be shorter than printed books?
2025-04-09 19:10:54 <thrig       > vim has more code in header files than vi does in total
2025-04-09 19:46:51 <cleobuline  > mforth:  : test  DUP
2025-04-09 19:47:00 <cleobuline  > mforth:  DUP
2025-04-09 19:47:13 <cleobuline  > mforth:   *  * ;
2025-04-09 19:47:32 <cleobuline  > mforth:  3 test .
2025-04-09 19:47:32 <mforth      > 27
2025-04-09 19:51:50 <nmz         > what's a byte?
2025-04-09 19:52:31 <nmz         > yall deal with weird machines, I recently learned that a byte was the smallest addressable value, so, then, it changes? its not always 8
2025-04-09 19:52:44 <xentrac     > not always addressable, no
2025-04-09 19:53:15 <xentrac     > lots of word-oriented machines had bytes of 6-9 bits within a word
2025-04-09 19:53:34 <nmz         > but it seems that a byte now means 8bits, not smallest addressable value, so then, what should that be called
2025-04-09 19:53:43 <xentrac     > "octet"
2025-04-09 19:53:48 <nmz         > I really need a dictionary because its driving me insane
2025-04-09 19:54:16 <xentrac     > or do you mean what should the smallest addressable value be called?
2025-04-09 19:54:24 <nmz         > I looked around, and then a "word" is 16 in x86 and nothing else, really, there is no standardization and I don't even know what anything means anymore
2025-04-09 19:54:33 <xentrac     > historically it was "memory word"
2025-04-09 19:54:52 <nmz         > 
ACTION is learning

2025-04-09 19:55:32 <xentrac     > words were also 16 bits in DG NOVA, PDP-11, MSP430, TMS9900, Tandem, Xerox Alto, and I think 65816
2025-04-09 19:56:04 <xentrac     > of those, some but not all had byte-addressable memory
2025-04-09 19:56:21 <xentrac     > Stretch and B5000 had bit-addressable memory IIRC
2025-04-09 19:57:04 <xentrac     > you could go with "address unit" if you want to avoid "word", as you probably should
2025-04-09 19:58:57 <xentrac     > normally a "word" is the size of an arithmetic operand, but old decimal computers (for business accounting) often had arbitrary-precision arithmetic and digit-addressable memory
2025-04-09 20:37:47 <MrMobius    > you can just call them bytes. no one in actual practice would say byte and mean anything other than 8 bits without clarifying
2025-04-09 20:38:18 <MrMobius    > even if C doesn't always mean 8 bits in the documentation
2025-04-09 21:06:16 <nmz         > MrMobius: but that's my dislike
2025-04-09 21:28:51 <xentrac     > nmz: you could make up a word
2025-04-09 21:32:42 <xentrac     > $ ~/dev3/vecmarkov.py < ~/netbook-misc-devel/bible-pg10.txt | tr -cs A-Za-z '\n'| fgrep -vxf /usr/share/dict/words
2025-04-09 21:34:05 <xentrac     > offers suggestions such as "ilt", "cousit", "warikin", "thad", "paupe", "wid", "tus", and "tond"
2025-04-09 21:34:46 <xentrac     > these being http://canonical.org/~kragen/sw/dev3/vecmarkov.py and http://canonical.org/~kragen/sw/netbook-misc-devel/bible-pg10.txt
2025-04-09 21:35:56 <xentrac     > I'd forgotten about the -x (--line-regexp) option
2025-04-09 22:29:20 <nmz         > got it, bitsy
2025-04-09 23:18:51 <veltas      > Interestingly I think it's unlawful for me to view that bible
2025-04-09 23:20:44 <veltas      > In the UK it is protected by a perpetual royal prerogative, but in the rest of the world it's public domain
2025-04-09 23:28:09 <veltas      > I've got a lawful copy though, of course