100phlecs

> an opportunity to try and clean up the AST and/or try to make it compatible with other text markup parsers and html/pdf/whatever generators. [Maybe CommonDoc could be the foundation...

For those on M1, you'll need to create the directory. Since the [homebrew path](https://github.com/Homebrew/brew/issues/9177) in M1 land is `/opt/homebrew` instead of `/usr/local` The current openssl path is hardcoded. https://github.com/gambit/gambit/issues/512 https://github.com/gambit/gambit/pull/638...

An opinionated guide that takes full advantage of the bleeding edge features, like flakes & new CLI, sounds awesome and is exactly what I would be looking for as a...

Here's a [related talk](https://youtu.be/PUv66718DII) that explores "an immediate connection to your creation" with programming. Has some interesting examples.

Current workaround is to put `hx-boost="false"` on the links. +1 on getting this fixed though. I discovered that when the document byte size is too large, it will prematurely resolve...

Did you ever figure this out? It's possible some internals have changed within the TailwindCSS lib 🤔

The current context behind this decision is [that it seemed complicated to determine](https://github.com/100phlecs/tailwind_formatter/pull/33) whether a string needs padding or not, i.e. `{"h-6 " if true, do: "bg-white"}` – a trailing...

Did you try `mix deps.compile tailwind_formatter --force`? I would be curious what your current use-case is, unless it's just loading in the custom classes for the first time Unfortunate that...

Would be nice for things to "just work" and not have to keep a mental checklist of when to run force recompilation for sure. I can see how just doing...

Fixed with https://github.com/100phlecs/tailwind_formatter/commit/1595240a2cb49d2f9ea5a573afb10c3f5a2f767d but leaving this issue open in case of other conflicts. If there are enough conflicts, then an alternative sorting approach may be the best path.