In `#lang pollen`, which uses a variant of at-expressions, you can change the
command character on a per-source-file basis, so you can say `◊(+ 1 1)` or `∆(+
1 1)` or `@(+ 1 1)` ...
I'm trying to figure out if I can bubble this up to DrRacket for syntax
coloring. I see two wrinkles:
1) For
context information (via the
> "mode" argument and the last result) and so that can be extended to
> track whether or not the character has been seen yet and, if it has,
> what it is.
>
> Robby
>
>
> On Fri, Nov 27, 2015 at 10:09 AM, MB wrote:
> > In `#lan
> Duplication is an uncomfortably common problem in Lispy circles, but
> fragmentation is never a good thing
To be fair, there are plenty of good reasons why duplication / fragmentation
would exist, many of them ultimately beneficial to the underlying system.
Fragmentation is not per se bad.
I don't know if that's a separate error. I've assumed that it's a side effect
of the build failing (= no docs end up where they're expected to be)
On Saturday, August 1, 2015 at 9:02:43 AM UTC-7, Andrew Gwozdziewycz wrote:
Possibly related? http://pkg-build.racket-lang.org/doc/pollen fails
4 matches
Mail list logo
