Commits on Nov 17, 2014
  1. Add a README

    This is the same README used by other bundles under the textmate organization.
    aroben committed Nov 17, 2014
Commits on Jun 18, 2014
  1. Point to ruby 1.8 shim

    Using a shim allows us to catch when 1.8 of ruby is not present and provide other options.
    infininight committed Jun 18, 2014
Commits on Mar 12, 2014
  1. Re-use existing (potentially busy) output window

    This requires 2.0-alpha.9519, although previously TextMate would not open multiple output windows.
    sorbits committed Mar 12, 2014
Commits on Jul 27, 2013
  1. Use version 1.8 of ruby for bundle items

    10.7 and 10.8 only include ruby 1.8, so all bundle items have been written to work with that. Optionally supporting ruby 1.9 and 2.0 is problematic as these versions are not fully backwards compatible.
    infininight committed Jul 27, 2013
Commits on Jul 4, 2013
  1. Fix working directory when calling ninja

    Due to a recent change in TextMate.executor it would always change the working directory to the project directory, which would fail if TM_NINJA_FILE was set to a file outside that folder and was using relative paths.
    sorbits committed Jul 4, 2013
Commits on Jan 13, 2013
  1. Show build completion progress in status bar

    This is done via the TextMate JavaScript object which has a ‘progress’ property that can be used to control the progress indicator in the status bar. In TextMate see ‘Help → JavaScript Object’ for more information about this object.
    sorbits committed Jan 12, 2013
  2. Simplify build command by relying on TextMate.executor

    There also was some clumsy/redundant code which has now been removed.
    sorbits committed Jan 10, 2013
Commits on Sep 26, 2012
  1. Add requiredCommands section

    This avoids having the user explicitly set PATH or TM_NINJA.
    sorbits committed Sep 26, 2012
  2. Fix version argument given to ninja

    The ‘-V’ argument does not exist with ninja 1.0.0.
    sorbits committed Sep 26, 2012
Commits on Sep 14, 2012
  1. Switch paste behavior

    The simple paste behavior is better suited to indent-based languages like ninja.
    sorbits committed Sep 14, 2012
Commits on Sep 10, 2012
Commits on Aug 24, 2012
  1. Mark leading tabs as invalid

    We do allow leading tabs when followed by a comment — the description of the Ninja language lack information about how comments are defined and it also lack info about this rule about indent having to be done with spaces, but it seems to be an oversight — grammar may need to be revised based on the actual implementation of Ninja.
    sorbits committed Aug 24, 2012
Commits on Aug 19, 2012
  1. Don’t override ⌘B if there is a selection (in text)

    The motivation for this is that ⌘B in markup languages (which should have a text scope) are bound to “Format → Bold”, which is an action that primarily is used with a selection. So by scoping the Ninja build command to only the case where there is no selection (in the text scope), we can have both Bold and Build coexist in markup languages.
    Since users may not realize that it is having a selection that stops ⌘B from working, I have limited this “feature” to the text scope, so in source files (where ⌘B for Build sees its primary use) we can still use ⌘B to build with a selection.
    sorbits committed Aug 19, 2012
Commits on Aug 4, 2012
  1. Comments are only allowed at the start of a line.

    Also add rules for the few ninja keywords.
    sorbits committed Aug 4, 2012
Commits on Jul 29, 2012
Commits on Jul 28, 2012
  1. Add simple indentation support.

    Presently we just increase indent after a ‘rule’ line.
    sorbits committed Jul 28, 2012
  2. Fix claimed file extension.

    sorbits committed Jul 28, 2012
Commits on Jul 26, 2012
  1. Add comment settings.

    sorbits committed Jul 26, 2012
Commits on Jul 25, 2012
  1. Initial commit

    sorbits committed Jul 25, 2012