Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jun 1, 2015
  1. @siddharthist
Commits on May 30, 2015
  1. @siddharthist

    Fixed typo

    siddharthist authored
  2. @siddharthist

    Added syntax highlighting for two functions

    siddharthist authored
    bytes->string/utf-8 and string-normalize-spaces
Commits on May 11, 2015
Commits on Jul 4, 2014
  1. @goffrie
  2. @goffrie

    Fix quote highlighting

    goffrie authored
Commits on Jun 21, 2014
  1. @goffrie

    Heredocs and #\] characters

    goffrie authored
Commits on Mar 24, 2014
  1. @rodrigosetti

    Adds spell checking for comments

    rodrigosetti authored
    By adding `@Spell` and leaving `syn spell default`, Vim will check spell checking only in comments and nowhere else.
Commits on Dec 23, 2013
  1. @Yuhta

    Add multiple values

    Yuhta authored
Commits on Dec 22, 2013
  1. @Yuhta

    Add module* and module+

    Yuhta authored
Commits on Mar 23, 2013
  1. @LnL7
Commits on Jan 30, 2013
  1. fix incorrect highlighting

    authored
Commits on Dec 23, 2012
Commits on Oct 16, 2012
  1. @nathanpc

    Added "Writing" to the syntax

    nathanpc authored
  2. @nathanpc
Commits on Sep 17, 2012
  1. add section 5.4

    authored
  2. add section 5.3

    authored
  3. add section 5.2

    authored
Commits on Feb 18, 2012
Commits on Oct 10, 2011
  1. add section 4.4

    authored
  2. add section 4.2

    authored
  3. add struct

    authored
Commits on Sep 20, 2011
  1. @thepaul

    add "define-syntax-rule" keyword

    thepaul authored committed
Commits on Aug 9, 2011
  1. @takikawa
  2. @takikawa
  3. @takikawa

    Add racket/set keywords.

    takikawa authored
  4. @takikawa

    Add racket/function keywords

    takikawa authored
Commits on Jun 9, 2011
  1. @thepaul
  2. @thepaul
  3. @thepaul
Commits on Jun 8, 2011
  1. @thepaul

    fix syntax highlighting a lot more

    thepaul authored
    this fixes the previous beast of number highlighting (which broke some
    unrelated things, and wasn't complete) with a new beast.  this beast,
    however, is believed to be complete for Racket numbers.
    
    also in this commit, lots of cleanup of stray syntax rules that were
    inefficiently specified or plain incorrect.  adjust region match area for
    all parenthesized/bracketed highlight patterns, so that their contents
    get matched correctly as well.  use \k where it makes more sense than
    long [everypossiblecharacter] collection matches.  add the other
    "#\specialchar" patterns.
    
    still to do: change group linking around so that quoted areas are more
    easily distinguishable from non-quoted areas.
  2. @thepaul

    Revamp number highlighting

    thepaul authored
    Words which start like numbers but which are not syntactically valid
    numbers on the whole are treated by Racket as normal identifiers.  This
    change highlights them as such, and adds some recognition of a few extra
    number syntaxes not previously recognized.
    
    Also add "number-syntax-test.rkt", which has a bunch of test expressions
    which one can load manually in vim to make sure things are highlighted
    as expected when something changes.
    
    The approach to syntax matching taken here is not as clean as I'd like.
    The syntax specification for numbers in Racket is rather complex, and
    when I build a few large regular expression to handle all of it, vim
    complained about there being too many \(\)s!  Now, instead, we match
    sequences of characters which might be valid numbers, and then try to
    detect invalid sequences of characters in contained match regions.  If
    a sequence turns out not to be a number after all, and it wasn't
    qualified with a radix specifier like #d or #x, then overlay it with
    transparent non-highlightery with its own contains=TOP.
    
    This doesn't (and possibly can't, efficiently) identify all possible
    invalid numbers, but it does get a lot.
  3. @thepaul

    recognize #\return

    thepaul authored
Something went wrong with that request. Please try again.