Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Apr 10, 2015
  1. Fix incredibly clowny mis-nesting

    Because we were rescuing within the class body and not the method body,
    Watchman errors were bubbling up uncaught.
    I think this has been broken since 542ccd4, suggesting I need a
    regression test, which I will try and follow up with later.
  2. Improve Watchman error messages

    This isn't just about "unavailability". Let the Watchman error messages
    show through in the exception text; it may be helpful, such as:
    > CommandT::Scanner::FileScanner::WatchmanFileScanner::WatchmanError:
    > unable to resolve root [PATH]: none of the files listed in global
    > config root_restrict_files are present
Commits on Apr 9, 2015
  1. Make autocmd set-up consistent

    Put the `MatchWindow` autocmds in a group, and make the group names
    consistent across the project. Note that we don't need to worry about
    the `MatchWindow` autocmds leaking in normal use, because the window
    hangs around in the background and gets re-used.
Commits on Mar 17, 2015
Commits on Mar 11, 2015
  1. Doc: update AUTHORS

  2. Merge branch 'gh/ZyX-I/status-methods' into next

    * gh/ZyX-I/status-methods:
      Git: update .mailmap
      Clean up status-line methods
      Add methods useful for status lines
  3. Git: update .mailmap

  4. Clean up status-line methods

    One substantive fix in here:
    - add missing (unbalanced) paren in `commandt#CommandTPath` method
    And some other consistency/polish tweaks:
    - add some comments indicating what the added methods are for
    - use `&&` instead of `and`
    - remove redundant explicit `if`/`return true`/`else`/`return false`
    - allow `#path` and `#active_finder` methods to return `nil`; one of
      these requires a change to the caller to preserve desired behavior,
      but the other one can be left as-is (interpolating `nil` in a string
      is a no-op)
    - use parens around method parameter lists
  5. @ZyX-I

    Add methods useful for status lines

    ZyX-I authored committed
Commits on Mar 6, 2015
  1. Don't create empty class bodies

    Lurking on the Unicorn mailing list, I learnt that by avoiding creating
    a heavyweight class definition scope, you can save a couple hundred
Commits on Feb 28, 2015
  1. Merge branch 'gh/mathstuf/git-submodule-scan' into next

    Originally submitted at:
    * gh/mathstuf/git-submodule-scan:
      doc: Update for the new g:CommandTGitScanSubmodules option
      Make @scan_submodules code work
      Expect g:CommandTGitScanSubmodules to be a boolean
      git: add option for scanning submodules
  2. doc: Update for the new g:CommandTGitScanSubmodules option

    - whitespace fix
    - minor rewording, adding a link back to the `g:CommandTFileScanner`
    - updated HISTORY and AUTHORS sections
  3. Make @scan_submodules code work

    Based on mathstuf@e8c68da, but
Commits on Feb 10, 2015
  1. Update copyright year ranges

Commits on Feb 9, 2015
  1. Merge branch 'blueyed/fix-rxvt' into next

    * blueyed/fix-rxvt:
      doc: Update HISTORY for Daniel's rxvt patch
      Add `rxvt` to the pattern for terms where Escape should not be mapped
    Originally submitted at:
  2. @blueyed

    Add `rxvt` to the pattern for terms where Escape should not be mapped

    blueyed authored committed
    Originally submitted in relation to:
    For some reason, had a merge conflict, so in applying it, I took the
    opportunity to alphabetize the alternatives within the regex.
    Signed-off-by: Greg Hurrell <>
  3. Merge branch 'blueyed/highlight-fix' into next

    * blueyed/highlight-fix:
      doc: Add info to HISTORY section for Daniel's patch
      DRY up repeated `#gsub` calls in `#get_cursor_highlight`
      Only use `highlight!` when needed
      Teach get_cursor_highlight to return an array
      Clean-up comments in MatchWindow#get_cursor_highlight
      Fix handling output of ":hi Cursor" with link + definition
    Originally submitted at:
    With some follow-up from me.
  4. Only use `highlight!` when needed

    As mentioned in ab15fa2, we previously used `:highlight` for
    everything, but the need to use `:highlight!` for some specific cases
    led us to use `:highlight!` for everything.
    This commit makes things a little more nuanced by marking the specific
    cases that need the bang, and using it only in those cases.
  5. Teach get_cursor_highlight to return an array

    As of cfd65e2 `#get_cursor_highlight` may actually return more than one
    `:highlight` command in order to support restoring highlights that
    involve patterns like:
      :highlight! link Cursor VisualNOS
    Rather than returning a string with another command tacked on, let's
    just always return an array.
    The one possible gotcha here is that this kind of rule must be set up
    using `:highlight!` and not `:highlight`, or Vim will complain with:
      E414: group has settings, highlight link ignored
    So, this commit changes the `#show_cursor` to always use `:highlight!`
    instead of `:highlight`. It's possible this might have unintended
    side-effects, so I'm going to follow up with a tweak that makes it a
    little more nuanced.
  6. @blueyed

    Fix handling output of ":hi Cursor" with link + definition

    blueyed authored committed
    This gets set up through my solarized theme:
        hi! link Cursor VisualNOS
    `:hi Cursor` looks as follows then:
        Cursor         xxx ctermfg=8 ctermbg=12 guifg=bg guibg=fg
                           links to VisualNOS
    Without this patch there's the following error when closing the match
      > Error detected while processing function CommandTCancel:
      > line    1:
      > E416: missing equal sign: links to VisualNOS
    This uses a hack to apply two `highlight` commands, and should maybe get
    improved to return and handle a list of highlight definitions.
Commits on Feb 6, 2015
  1. @mathstuf
Commits on Feb 4, 2015
  1. doc: Mention Nicholas T's pull request in the HISTORY section

    Forgot to do this earlier.
  2. Add g:CommandTEncoding option

    This is a hacky workaround for:
    And most users will never need to use it, but the impact is relatively
    low so I'm going to include it anyway.
  3. Merge branch 'NicholasTD07/rvm-doc' into next

    * NicholasTD07/rvm-doc:
      Git: add Nicholas T. to the .mailmap file
      doc: Add Nicholas T. to the AUTHORS section
      doc: Add more details about setting Ruby verisons
  4. @NicholasTD07

    doc: Add more details about setting Ruby verisons

    NicholasTD07 authored committed
    Originally submitted as:
    Original message:
    > If you are an RVM or rbenv user, CommandT has to be built and run with
    > the same version of Ruby that Vim is linked against. Otherwise
    > CommandT won't work. So you either have to set that version of Ruby as
    > default or you need to re-build Vim with a version of Ruby you prefer.
    I tweaked the wording a little (for example, "built and run" doesn't
    really make sense, as you build Command-T but run Vim) and weakened the
    recommendation to from setting a global default Ruby version to setting
    a temporary local override (the whole point of Ruby version managers is
    that you _don't_ have to make global settings like that just to get one
    specific piece of software to work).
    Signed-off-by: Greg Hurrell <>
Something went wrong with that request. Please try again.