i use https://github.com/sirmalloc/ccstatusline and when im around 100k tokens im already thinking about summarizing where we're at in the work so i can start fresh with it
it is pretty rare for me to compact, even if i let it run to 160k
--
just realized how i wouldn't think about using ccstatusline based a quick glance at its README's images. looks like this for me:
I've always found OCaml's (* ... *) comments annoying, because it needs shift for both characters. But I suspect it's easier to type on a french keyboard.
Keyboards of early MIT systems[1] and Lisp Machines[2] had brackets (parentheses) and square brackets on the same key where square brackets and curly brackets are on modern keyboards.
hi. i run "ocr" with dmenu on linux, that triggers maim where i make a visual selection. a push notification shows the body (nice indicator of a whiff), but also it's on my clipboard
> As far as tooling limitations, GZDoom is not a bed of roses. Very little in the engine is runtime editable, so you have to reload the engine to see any of your changes. A rapid turnaround time for reloading changes is nice but it's far better to have as much as possible live-update. And ideally, in my opinion, you have the editor built into the engine itself, and you can do much of what you need from there without having to jump around to outside programs. Playscii was my first big attempt to build a little environment like that, something you can think in once you learn it well enough, like a musical instrument. Miles to go but that's always where I'm trying to get to.
I will never use this platform. i didn't even click into it. pathetically, i did click to view comments
But I think commenting on someone's bio is the kinda harshness you only do in the moment. the kinda thing I'd approach differently in hindsight (one that isn't an attempt to be cruel)
that current etymology is what we’re all talking about obv
reply