Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Nov 23, 2010
  1. @mikewest
Commits on Nov 22, 2010
  1. @mikewest
  2. @mikewest

    Merge branch 'blockcomments'

    mikewest authored
  3. @mikewest

    Normalizing leading space in comments

    mikewest authored
    That is:
        def function:
                This is a comment
                with _lots_ of leading
                space!  OMG!
    Will parse into:
                [   "This is a comment",
                    "with _lots_ of leading",
                    "space!  OMG!"
  4. @mikewest
  5. @mikewest
  6. @mikewest

    Block comment parsing: basics.

    mikewest authored
    Block comments are parsed out, but the commentchar removal isn't working
    yet.  I'll refactor that code out of it's current home, and move it into
    `parse`, as I need to know what _kind_ of comment it is that I'm
    stripping.  Carrying that metadata around doesn't make any sense, so
    I'll just convert the comment on the fly into a set of non-comment
Commits on Nov 21, 2010
  1. @mikewest
  2. @mikewest

    Adding Ruby block comment syntax.

    mikewest authored
    Working towards GH-22.
  3. @vast @mikewest

    Really fixing extensionless file support

    vast authored mikewest committed
    Pieced together a fix using Regex and `File.extname` from
    Closes GH-24.
  4. @mikewest

    Locking the CSS file down to Docco's v0.3.0

    mikewest authored
    I'm a bit loath to change the rendering entirely without talking to
    Ryan, but I'd really prefer to replicate Docco's CSS file generation
    rather than hotlinking out to the GitHub-hosted version.  Offline
    support would require it, if for no other reason...
    Closes GH-23.  Thanks to [Myles Byrne](
Commits on Oct 24, 2010
  1. @mikewest
Commits on Oct 21, 2010
  1. @mikewest

    Skipping Python/Ruby 1.9 source encoding

    mikewest authored
    In the same way that it makes sense to skip the shebang (#!) line in
    scripts, it makes sense to skip the encoding definition in Python files
    (described by [PEP 263][p]) and Ruby 1.9 files (similar enough syntax
    that it's not worth worrying about.
  2. @mikewest
Commits on Oct 20, 2010
  1. @mikewest

    Merge branch 'language'

    mikewest authored
  2. @mikewest
  3. @mikewest

    Autopopulate comment_chars for known languages

    mikewest authored
    Adding comment characters for bash, c, c++, coffee script, java, javascript, lua, python, ruby, and scheme.  Paving the way for block-comment parsing later on...
    Closes issue #20.
  4. @mikewest

    Attempt to autodetect file language

    mikewest authored
    `pygmentize` 1.0+ has an `-N` option that attempts to match a file (via
    the extension) to a language lexer.  If `pygmentize` is installed, we'll
    run it with this option to get a language.
    If no language is detected, `pygmentize -N` returns `text`.  In that case,
    we'll first look for a user-provided language to use as a fallback.  If no
    language was provided, highlight using `ruby` as a reasonable default.
    Closes issue #19.
  5. @mikewest

    Typo: Closes issue #11

    mikewest authored
    Thanks to Paul Chavard ( ) for
    the report and fix.
Commits on Oct 19, 2010
  1. @mikewest

    Specify encoding for Pygments

    mikewest authored
    This closes issue #10, in theory, but I'm not completely happy with the
    behavior.  The output for both UTF-8 and ISO-8859-1 sources is arguably
    correct, but I think it'd be better to do some autodetecting of the file
    encoding, and explicitly convert everything to UTF-8 on input.  One
    option is the [`chardet` gem][gem], but I'm loath to add another
    dependency to Rocco...
  2. @mikewest

    Cleaning up tests after bugfix merges:

    mikewest authored
    As a result of fixing issue #15, a few tests broken.  This commit brings
    the tests up to date with the latest behavior.
  3. @rtomayko

    task :default => :test

    rtomayko authored
  4. @rtomayko
  5. @rtomayko

    Merge remote branch 'mikewest/template'

    rtomayko authored
  6. @rtomayko
Commits on Oct 17, 2010
  1. @mikewest

    Adding a basic test suite.

    mikewest authored
  2. @mikewest

    Variables for use in Mustache templates.

    mikewest authored
    *   `docs?`:    True if `docs` contains text of any sort, False if
                    it's empty.
    *   `code?`:    True if `code` contains text of any sort, False if
                    it's empty.
    *   `empty?`:   True if both `code` and `docs` are empty.  False
    *   `header?`:  True if `docs` contains _only_ a HTML header.  False
  3. @mikewest

    Adding CLI argument `template`

    mikewest authored
    In v0.5, the Mustache template is hardcoded as
    `./lib/rocco/layout.mustache`.  This makes it quite difficult to
    style generated content as one must edit the layout file inside the
    gem itself to make changes.
    I propose leaving that file as a sensible default, but allowing the user
    to specify an absolute or relative (to the current working directory)
    path to a mustach template of her choosing.  That's implemented in this
Commits on Oct 14, 2010
  1. @mikewest

    Fixing (among other things) alternate header syntax

    mikewest authored
    The following works in Docco, but not in Rocco:
        Level 1 Heading
        Level 2 Heading
    Happily, the fix is trivial.  In Docco, the regex for comments is:
        # Does the line begin with a comment?
        l.comment_matcher = new RegExp('^\\s*' + l.symbol + '\\s?')
    Changing Rocco's comment pattern to:
        @comment_pattern ="^\\s*#{@options[:comment_chars]}\s?")
    Solves the problem for me.
  2. @mikewest

    Fixing code highlighting in bash mode

    mikewest authored
    Rocco splits against `<span class="c.">`, which works fine for Ruby
    where the `span` has a class of `c1`, but fails for Bash (and probably
    other languages), where the `span` has a class of `c`.  The fix is
  3. @mikewest

    Integrate `pilcrow` change from Docco

    mikewest authored
    Rocco uses the Docco CSS directly, so when they make an update to the
    HTML/CSS, Rocco needs to play along.  In this case, Docco changed from
    `#` to `¶`, and changed classnames as well (in
    This commit migrates that change to Rocco.
Commits on Sep 10, 2010
  1. @rtomayko

    0.5 release

    rtomayko authored
Commits on Apr 3, 2010
  1. @evaryont @rtomayko
Commits on Apr 2, 2010
  1. @rtomayko
  2. @rtomayko

    avoid which(1)

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