> It looks like > you have to be able to run the config submodule of some program to be > able to figure out how to syntax color it?
Right, that's the way the config logic works, and I'm trying to figure out how to hook the syntax colorer into that logic. > That's not generally something that is well-supported, > although I suppose you could make it work. Racket encourages high levels of optimism ;) > The usual way we deal with configuration at that level would be to > allow someone to write, say. > > #lang pollen command-char ☺ I looked at doing it that way, but ... multiplied across a large project — Pollen tends to encourage lots of small source files rather than fewer large ones — it felt more ergonomic / consistent to keep all the user-configurable options in one location (like an .rc file). (Rather than, say, trying to jam into the #lang line, or having certain options on the #lang line and the rest elsewhere.) -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
