Skip to content
Commits on May 19, 2016
  1. Fix for #117

    committed May 19, 2016
Commits on May 18, 2016
  1. Fix for #116. Create highlight groups intelligently i.e. avoid clobbe…

    …ring any existing definitions and create upon VimEnter to base it off of the colorscheme used
    committed May 18, 2016
Commits on Apr 9, 2016
  1. Added support for listing global marks

    Due to a lot of changes I was unable to merge in #89.
    Hopefully, this fixes #88
    * Renamed SignatureListMarks to SignatureListBufferMarks
    * Added new command SignatureListGlobalMarks
    * Rewrote the List() functions to hopefully make it cleaner and easier to understand
    * Added boundary checks when showing lines with context
    * Replaced stringified args to the signature#mark#List() function with 0/1 to denote scope.
    * Removed inconsistent use of v:count in ListBufferMarks map.
      v:count was being used to indicate lines of context while everywhere else v:count is used to select a marker
    * Added v:count to select a particular marker to List as it'd be consistent with other uses of v:count
    committed Apr 10, 2016
  2. Removed location list related maps

    There are a couple of reasons why I don't like the existing code:
    1. Those maps affect the location list/quickfix and have nothing to do with Signature as such.
    2. It creates a division in how location list/quickfix is used. Those mappings only work when invoked by Signature and not with other plugins.
    Pull request  #110
    committed Apr 9, 2016
Commits on Mar 16, 2016
Commits on Mar 11, 2016
  1. Fix for #93

    committed Mar 11, 2016
  2. Updated doc

    committed Mar 11, 2016
  3. Created Signature highlight groups to be used by themes

    Created highlight groups SignatureMarkText, SignatureMarkLine, SignatureMarkerText and SignatureMarkerLine
    This should hopefully simplify the colorscheme code and allow it to remain blissfully ignorant of Signature code
    Additionally, creation of these highlight groups allows me to use it as a fallback option in the following scenario
    Let's say g:SignatureMarkTextHLDynamic=1 and we're on a line that doesn't have any changes, so no signs are placed by
    GitGutter or Signify. In this case, Signature needs a fallback option and that's where these highlight groups come in.
    By default, these are linked to "Exception" and "WarningMsg" to preserve the traditional behavior.
    If required, colorschemes can link it to something else and thereby have the signs fit into their scheme.
    committed Mar 11, 2016
  4. Removed eval; replaced stridx with match

    Since I'm using type() now to determine if g:SignatureMark*HL is a string
    or a Funcref, eval is not necessary once I know it's a string.
    This allows me to get rid of the horrible double quotes
    Converted all stridx to string match
    committed Mar 11, 2016
Commits on Mar 3, 2016
  1. Merge pull request #108 from Barthalion/signify-hlgroup

    Use Signify highlight groups instead of Diff
    committed Mar 3, 2016
  2. @Barthalion

    Use Signify highlight groups instead of Diff

    User might have customized Signify highlight groups. This commit
    makes Signature respect that.
    Barthalion committed Mar 3, 2016
Commits on Feb 21, 2016
Commits on Feb 8, 2016
  1. Modified logic to ensure that ToggleDummy() gets called whenever the …

    …last sign gets removed
    committed Feb 8, 2016
Commits on Feb 6, 2016
Commits on Feb 5, 2016
  1. Added support for providing context while listing markers. Added supp…

    …ort for listing more than one marker but not all
    committed Feb 5, 2016
  2. Moved SignatureList* context code from signature#mark#GetList() to si…

    …gnature#mark#List() to keep the code local and to keep GetList clean
    committed Feb 5, 2016
  3. Merge pull request #105 from mMontu/Context2

    Allow context with :SignatureListMarks
    committed Feb 4, 2016
Commits on Jan 21, 2016
  1. @mMontu

    Allow context with :SignatureListMarks

    The `SignatureListMarks` and its mapping (`m/`) were changed to allow
    displaying context along the lines, similar to `:g/<patern>/z#=1`
    mMontu committed Jan 21, 2016
Commits on Nov 11, 2015
  1. Bugfix for #99 - Fixed list generation when a global mark is moved fr…

    …om one buffer to another
    committed Nov 11, 2015
Commits on Nov 7, 2015
  1. Removed functions from global scope (signature#...) if they were used…

    … locally. Moved mark.vim, marker.vim and sign.vim to the autoload folder
    committed Nov 7, 2015
Commits on Oct 10, 2015
  1. Merge pull request #96 from rafi/fix/custom-viminfo

    Fix #95 viminfo custom location
    committed Oct 10, 2015
Commits on Sep 17, 2015
  1. @rafi

    Fix #95 viminfo custom location

    rafi committed Sep 17, 2015
Commits on Jul 9, 2015
  1. Merge pull request #92 from rkennedy/function-reference

    Support function references and strings in highlight expressions
    committed Jul 8, 2015
Commits on Jul 8, 2015
  1. @rkennedy

    Support function references and strings in highlight expressions

    Retains compatibility with existing configurations, but also supports
    Vim function references.
    rkennedy committed Jul 8, 2015
Commits on May 19, 2015
  1. Merge pull request #86 from rburny/patch-1

    Don't remap <Esc> in location list.
    committed May 19, 2015
Commits on May 18, 2015
  1. @rburny

    Don't remap <Esc> in location list.

    I would suggest to not remap <Esc> (or do so optionally). Escape is a prefix to many keycodes, like arrow keys, and remapping it breaks them.
    rburny committed May 18, 2015
Commits on Apr 25, 2015
Commits on Apr 14, 2015
  1. Readded the .gitignore file

    committed Apr 13, 2015
Commits on Apr 11, 2015
  1. Why do I need a gitignore?

    committed Apr 11, 2015
  2. Added support to color signs using highlight groups defined by vim-gi…

    …tgutter and vim-signify
    committed Apr 10, 2015
Something went wrong with that request. Please try again.