Now that (make-scribble-inside-lexer #:command-char #\◊) exists in Racket version 6.2.
(uses dynamic-require so that it doesn't break it for other versions)
Now that `(make-scribble-inside-lexer #:command-char #\◊)` exists in Racket version 6.2.
(uses dynamic-require so that it doesn't break it for other versions)
In DrRacket, it means that the text in a pollen source file will be colored just like scribble content except that it treats ◊ as the command character instead of @.
In DrRacket, it means that the text in a pollen source file will be colored just like scribble content except that it treats `◊` as the command character instead of `@`.
Either way, the Pollen coloring doesn't match Scribble (see the text in the curly braces, and the color of the escape character).
Do you see something different?
Without the patch, I see this:
![patch reverted](https://cloud.githubusercontent.com/assets/1425051/8266161/a0af8d66-16d2-11e5-9424-b85aec977a32.gif)
With the patch, I see the same thing:
![patch applied](https://cloud.githubusercontent.com/assets/1425051/8266162/a4160ba6-16d2-11e5-85f5-70a0c638203f.gif)
Either way, the Pollen coloring doesn't match Scribble (see the text in the curly braces, and the color of the escape character).
Do you see something different?
Now that
(make-scribble-inside-lexer #:command-char #\◊)
exists in Racket version 6.2.(uses dynamic-require so that it doesn't break it for other versions)
Thanks. What does this do?
In DrRacket, it means that the text in a pollen source file will be colored just like scribble content except that it treats
◊
as the command character instead of@
.Without the patch, I see this:
With the patch, I see the same thing:
Either way, the Pollen coloring doesn't match Scribble (see the text in the curly braces, and the color of the escape character).
Do you see something different?
You probably have to restart DrRacket, and possibly run raco setup (that's what I ended up having to do).
OK, I see it now. Very good. Thanks again.
963c5de3b2
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.