Hi all, I, for one, think this initiative is interesting. When I tried acme, the lack of syntax coloring was a big hindrance, I'm probably not the only one. This could lead to more adoption.
Now, LLMs companies are mostly evil, and LLM generated code is mostly shit, but with proper quality gates it can be OK. These tools are here to stay, and I think that Paul's method of seeing the *.md files as the source and the LLM process as a kind of preprocessor is the best way to go about it. I know that this community values the craft and prides itself on code quality. I use it as an example to strive for when I teach computer science, systems design, or programming, but compilers were once seen as LLMs are seen now (minus the copyright infringement and the ecological cost). Have you seen the output of the Go compiler for Hello world ? Yet go is an OK language for this community. There are ways to run open models on one own's hardware, and when doing so I use less electricity than I use to heat up my oven when I cook. We can avoid the ethical pitfalls, and learn how to put them to good use. I think Paul's approach of forking, being forward with the LLM use, and giving the prompts is a good standard to set to experiment with these. I see in your repo that this is going to be submitted to IWP9 :) I'm sorry I won't be able to be there, the discussions are going to be lively ! Looking forward to see where this is going. Cheers, Edouard. Paul Lalonde <[email protected]> writes: > I posted a week ago about the .md support and rich text I was getting > an LLM to build for me. > > I've updated it significantly. > > I still don't recommend reading the source, but it's now my > daily-driver and I do most of my markdown work in this now. It > supports editing reasonably well, acme-ideomatically, and lets you > directly type markdown annotations in-place, interpreting it as they > become usable. And when it's too bad, a quick B2 on the Markdeep tag > pops you into the regular text win that's backing the rich text. > > The rich text frame itself could probably be repurposed for other uses > (LSP comes to mind) as it merely tracks spans and does layout from > there, without knowledge of markdown itself. > > I'll note that it uses the font you currently have, building sizes, > bold and italics using crap naming heuristics. I usually invoke my > edwood with '-f /mnt/font/GoRegular/16a/font -F > /mnt/font/GoMono/16a/font' which gives me lots. If I invoke without, I > still get decent rendering, but the fonts and sizes are more limited. > > This is now in the mainline branch of my git repo: > https://github.com/paul-lalonde/edwood > > Issues welcomed. > > Paul ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T3af2222bdb4b9c14-M7b9f2bb01074fca40d780a9a Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
