Commits on Nov 14, 2017
  1. Fix minor readme typo

    taylorvance committed Nov 14, 2017
    "you" to "your"
Commits on Jun 20, 2017
Commits on Nov 28, 2016
  1. fix SuperTabLongestHighlight to only move the cursor when the complet…

    ervandew committed Nov 28, 2016
    …ion popup is visible
    fixes #162
Commits on Jan 3, 2016
Commits on Aug 28, 2015
Commits on Aug 24, 2015
  1. attempt to simplify configuration of completion chainging

    ervandew committed Aug 24, 2015
    update SuperTabChain to set the omni precedence and the default
    completion to 1 of the supported defaults and prevent overriding of that
    through calls to SuperTabSetCompletionType.
    refs #156
Commits on Aug 23, 2015
Commits on Aug 8, 2015
Commits on Jul 9, 2015
  1. add tracking of completion mode to alleviate reliance on pumvisible()

    ervandew committed Jul 9, 2015
    for users with a recent version of vim that don't use the completion
    menu, add support for tracking when completion mode is started/ended so
    that next/previous completions work correctly even when the completion
    menu isn't enabled.
Commits on Feb 15, 2015
  1. Use "inoremap" for "<C-x>" mapping

    blueyed committed Feb 15, 2015
    This is required when `<C-R>` is mapped itself, e.g. with peekaboo:
       i  <C-R>       * <C-O>:call peekaboo#peek(1, 'ctrl-r',  0)<CR>
Commits on Jan 15, 2015
Commits on Nov 18, 2014
  1. disable g:SuperTabCrMapping by default

    ervandew committed Nov 18, 2014
    This one feature causes more headaches than any other, with very little
    benefit to show for it.
  2. fix supertab <cr> map chaining logic

    ervandew committed Nov 18, 2014
    Looks like the logic for deciding if a cr should be issued by
    SelectCompletion has been wrong. Negating the previous logic seems to be
    what I had intended (unless there was some other edge case I'm
    refs #138
Commits on Nov 17, 2014
Commits on Oct 17, 2014
Commits on Aug 20, 2014
Commits on Aug 7, 2014
Commits on Aug 2, 2014
  1. release fix for possible infinite recursion on <bs>

    ervandew committed Aug 2, 2014
    when s:SuperTabNoCompleteAfter has been modified by the user, then eclim
    will remap <bs>. However a recent change[1] modify the s:CompletionReset
    code to call the second <bs> char as the mapped version, which if
    supertab has it mapped, results in an infinite loop under these
    fixes #120
    [1] c8c1876
Commits on Jul 4, 2014
  1. Fix a typo.

    earthday committed Jul 4, 2014
Commits on Jun 20, 2014
  1. fix handling of existing non-expr <s-tab> mapping

    ervandew committed Jun 20, 2014
    also remove some code duplication
    fixes #123
Commits on Jun 19, 2014
Commits on Jun 11, 2014
Commits on Jun 9, 2014
  1. SuperTabCodeComplete: handle dict return value from Func

    blueyed committed Jun 8, 2014
    If the first function in the chain returns a dict, instead of just a
    list of words, look at (the length of) results.words.
    NOTE: if results.refresh is set to "always" (as with YouCompleteMe), we
    might want to return the empty list anyway, which would allow the
    function to stay in the loop.
    > || (has_key(results, 'refresh') && results.refresh == 'always')
  2. CompletionReset: feed the original BS key with mapping enabled

    blueyed committed Jun 9, 2014
    Backspace might have been mapped by the user, and this should be
Commits on May 4, 2014
  1. de-indent the code blocks in the README

    ervandew committed May 4, 2014
    when indented they start looking more like quotes with a leading gray