In my previous post I talked about how Racket Mode now will often want the back end command server, before actually needing a live REPL — but it has to start a REPL anyway. This was bothering me. So I went on to address that. Doing so entailed reversing the I/O model for the back end. As a bonus, that set up fairly short strokes to supporting multiple REPLs.
During most of January and into February, I’ve been working full-time to have Racket Mode make better use of drracket/check-syntax analysis of fully-expanded code. I’m pretty excited by it.
For most of the last decade I’ve made things in Racket — including making tools and tutorials to support other people making things in Racket.
At RacketCon 2019, Aaron Turon gave the keynote about the Rust community.
That afternoon, I had a talk about Racket Mode for Emacs.
The next morning?
For the first time, ever, I’ve been using Linux on raw hardware for a couple months. The experience has been utterly boring and wonderful.
In racket-mode I improved support for the
multi-in form provided by
I’m writing and publishing this post using something other than Frog.
Having said that, I’m not planning to abandon maintaining Frog.
Sometimes people want Racket
threads to have useful names — for example to show in logger output. Here is one way to do it.
Even though it’s been one of my most time-consuming projects, I’ve hardly blogged about racket-mode — an Emacs major mode for Racket. To change that, here’s a post giving an overview of how racket-mode works, as well as a look at how it might grow someday.
In my previous post I discussed what I’m doing with deals.extramaze.com — and what I’m intentionally not doing. Since then, I’m not-doing more. This improves performance and simplifies the content security policy.
For Extramaze LLC I’m using Racket in a commercial project — a search engine with email alerts for deals on music gear — deals.extramaze.com.