[racket] Anyone familiar with mercurial? Add syntax coloring to github?

Wonderful!  This will make the github experience much nicer.

On Sun, Aug 12, 2012 at 6:36 PM, Greg Hendershott
<greghendershott at gmail.com> wrote:
> So I followed up on this.
>
> https://bitbucket.org/greghendershott/pygments-main/changeset/240e51e2da13b079482f6b61c215280224f89f06
>
> ~~~~~
> Add RacketLexer.
>
> Previously Racket files were handled by SchemeLexer. Instead, use a
> proper RacketLexer, which handles Racket more appropriately:
>
>  1. Treat square brackets like parentheses.
>  2. Expanded list of keywords.
>  3. Different file extensions, MIME types, etc.
>  4. Handle #:keyword arguments.
>  5. Handle more number literals (e.g. #xFF, #o777, 2e2, #e232, etc.).
>  6. Handle #| ... |# multiline comments (although NOT nested).
> ~~~~~
>
> Before I give them a pull request, I wanted to give folks here a
> chance to critique it (or even flatly veto it).
>
> Again, the goal is that eventually this would flow through to GitHub,
> and improve the readability of Racket repos and gists.
>
> On Thu, Jun 2, 2011 at 12:49 PM, John Clements
> <clements at brinckerhoff.org> wrote:
>>
>> On Jun 2, 2011, at 6:43 AM, Eli Barzilay wrote:
>>
>>> An hour ago, Vincent St-Amour wrote:
>>>> At Thu, 2 Jun 2011 06:30:00 -0400,
>>>> Greg Hendershott wrote:
>>>>>  aliases = ['scheme', 'scm', 'ss', 'racket', 'rkt']
>>>>
>>>> rktl would probably fit in there too.
>>>
>>> (This is just in case someone takes it on more seriously: IIRC,
>>> another issue with pygments was either ignoring square brackets, or
>>> highlighting them as errors.)
>>
>> Gosh, sounds complicated.  I don't think any of us could handle that!
>>
>>
>> John (goad, goad) Clements
>>
>>
>> _________________________________________________
>>   For list-related administrative tasks:
>>   http://lists.racket-lang.org/listinfo/users
> ____________________
>   Racket Users list:
>   http://lists.racket-lang.org/users



-- 
sam th
samth at ccs.neu.edu