[racket] How to associate a custom syntax color lexer with a new module language

Hi,

Everything works now. Thanks goes to Robby for adding
more debug info and to everyone who tried the code.

/Jens Axel


2012/6/23 Robby Findler <robby at eecs.northwestern.edu>:
> You can probably avoid starting up DrRacket to debug by calling
> read-language directly yourself, eg:
>
> (read-language (open-input-string "#lang ..."))
>
> Robby
>
> On Sat, Jun 23, 2012 at 5:59 AM, Jens Axel Søgaard
> <jensaxel at soegaard.net> wrote:
>> Hi Robby,
>>
>> Thanks for the change. Now I have a lead. I've got an
>> arity problem somewhere.
>>
>> /Jens Axel
>>
>>
>> 2012/6/22 Robby Findler <robby at eecs.northwestern.edu>:
>>> Okay, I've pushed a change that logs errors that read-language raises
>>> at the debug level. Hopefully it is helpful.
>>>
>>> Robby
>>>
>>> On Fri, Jun 22, 2012 at 9:44 AM, Jens Axel Søgaard
>>> <jensaxel at soegaard.net> wrote:
>>>> 2012/6/22 Robby Findler <robby at eecs.northwestern.edu>:
>>>>> Oh, duh. You're right of course.
>>>>>
>>>>> FWIW, DrRacket calls read-language on a port containing the contents
>>>>> of the definitions window. Probably the call you're interested in is
>>>>> in drracket/private/module-language-tools.rkt. If you see exceptions
>>>>> being swallowed there, then probably I coudl add some logging code to
>>>>> help others avoid these problems in the future.
>>>>
>>>> That might help. If it is a wrong-path problem, then it would
>>>> be useful to see the path in question.
>>>>
>>>> I am seeing some strange submodule/expansion errors, so
>>>> perhaps something is broken in my installation?
>>>> Although I downloaded the latest pre-prerelease the other day,
>>>> I think I'll try compiling from source (just in case).