I use Markdown/Markdeep syntax. The idea was so I can read my .md files and do basic chores with them in-place. The source text is all in body.all, and the renderer interprets that. I keep the selection aligned between the two in the hope I can come to copy/paste with markup semantics holding up. That's full of edge cases, but it's already useful enough that I'm now editing my .md docs for the AI in Edwood itself.
This is entirely eyes-off code. There is zero value, near as I can tell, in the code artifact. My specs and debug sessions have the value. This is largely an exercise in how to iterate on the spec to get a repeatable artifact as output, but that's still far from good - I don't have a sufficient way to automate the interaction testing. Paul On Mon, Jan 26, 2026 at 11:15 AM Shawn Rutledge <[email protected]> wrote: > > On Jan 26, 2026, at 07:21, Paul Lalonde <[email protected]> > wrote: > > > > I've wanted rich text in acme (well, Edwood) windows for a long time. > > Claude and enough specification seems entirely capable of doing what I > hadn't been able to find the time to do myself. Not ready for > distribution, and the code itself has negative value, but the suite of > tests and bundle of specs may have enough value to make this reproducible. > > Nice! > > But how do you specify the formatting? > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T3fa6a271939d2a0b-M163ab075e6ac11871ff07dba Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
