Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Mar 15, 2015
  1. Merge pull request #111: Give precedence to dynamic files over storag…

    authored
    …e by filetype
    
    I rewrote quite a bit of code in this pull request but I didn't change
    the behavior introduced by @cornerman (at least it was not my intention
    to do so). The main reason for rewriting was that the name
    xolox#easytags#get_global_tagsfile() "was a lie" because it could
    select either a file type specific tags files or the global tags file. I
    like functions whose name captures what they do so had to change things
    around in order to merge pull request 111 without having that name
    bother me :-).
    
    See also pull request 111 on GitHub:
      #111
    
    Which came forth from issue 102:
      #102
Commits on Nov 21, 2014
Commits on Nov 13, 2014
  1. Add g:easytags_opts option (issue #98)

    authored
    See also issue #98 on GitHub:
      #98
Commits on Sep 17, 2014
  1. Support for Perl highlighting (thanks to Jessica Kathleen McIntosh, s…

    authored
    …ee issue #97)
    
    See issue #97 on GitHub:
      #97
Commits on Aug 24, 2014
  1. @blukat29
Commits on Jul 19, 2014
  1. Use timers to identify slow[est] parts of vim-easytags

    authored
    See also #80 where I suggested
    to add accurate timing to the vim-easytags plug-in. Here it is :-). This
    is still quite rudimentary but it's already an improvement over what was
    there before!
Commits on Jul 8, 2014
  1. Support for keyword based syntax highlighting (much faster)

    authored
    See the following issues on GitHub:
     - #68
     - #80
    
    Please note that right now this 'feature' is not integrated with
    the "accelerated Python syntax highlighting" feature, because I'm
    considering ripping that out and replacing it with a *fast* Vim
    script implementation (if I can build one :-).
  2. Merge pull request #84: Asynchronous tags file updates! \o/

    authored
    This is part 1/2 of speeding up the vim-easytags plug-in. Refer to the
    pull request for details: #84
    In part 2/2 I want to speed up the dynamic syntax highlighting.
    Potentially related open issues on GitHub (probably missed a few):
    
     - #32
     - #41
     - #68
Commits on Jun 22, 2014
  1. Support for synchronous + asynchronous tags file updates (huge refact…

    authored
    …oring)
    
    See also pull request #49 for my previous and failed attempt:
      #49
Commits on Jun 16, 2014
Commits on Aug 19, 2013
Commits on Jul 16, 2013
  1. Merge pull request #59: Java interfaces support

    authored
    See pull request #59 on GitHub:
      #59
Commits on Jun 19, 2013
Commits on Jun 17, 2013
  1. Bug fix: Don't highlight C tags inside #if 0 (issue #57)

    authored
    $VIMRUNTIME/syntax/c.vim is a bit of a mess, I can't make heads or tails
    of it :-). In my simple #if 0 / #if 1 / #else tests this fixes the issue,
    but I'm not sure that there are no corner cases left.
    
    See issue #57 on GitHub:
      #57
Commits on May 25, 2013
Commits on May 23, 2013
Commits on May 19, 2013
  1. Document the g:easytags_events option (issue #46)

    authored
    Issue #46 on GitHub:
      #46
Commits on Apr 30, 2013
  1. Don't try to use dynamic tags files for non-writable directories (issue

    authored
    #29)
    
    This fixes the problem described here:
    #29
Commits on Apr 21, 2013
  1. Merge pull request #36

    authored
Commits on Apr 19, 2013
  1. Workaround low 'updatetime' intelligently

    authored
    This should hopefully resolve the following issues and pull
    requests: #31, #33, #42. I tried several of their suggestions
    in Vim 7.2 & 7.3 but it didn't work as it should IMHO.
    
    All of the issues and pull requests seem to imply that CursorHold
    events fire continuously when you set a low enough updatetime, but
    in my testing on Vim 7.2 and 7.3 this is not true. The event fires
    once, then Vim waits for user input before any new events fire.
    I'm not sure exactly what user input is required; moving the
    text cursor is not always enough but mode switching is.
    
    So what happens (in my testing) with all of the proposed solutions is
    that you stop typing for 'updatetime' milliseconds, the event fires, the
    plug-in simply increments or decrements a counter and then Vim just sits
    there doing absolutely nothing expect blinking the cursor...
    
    What I'm now trying instead is to remember the last time the plug-in was
    executed (the result of localtime()) and not acting on the CursorHold
    event until the following condition holds true:
    
      localtime() > (last_automatic_run + (easytags_updatetime_min/1000))
    
    I hope this provides a reliable solution. In any case it should be
    better than the previous annoying behavior :-)
Commits on Apr 18, 2013
  1. Move g:easytags_languages documentation to README.md

    authored
    Integration of pull request #40:
    #40
  2. Merge branch 'enh-languages' of git://github.com/inkarkat/vim-easytag…

    authored
    …s into inkarkat-enh-languages
Commits on Apr 17, 2013
Commits on Mar 7, 2013
  1. @inkarkat

    ENH: Allow to specify different ctags tool for particular languages.

    inkarkat authored
    Implement this via a new configuration option g:easytags_languages, a Dictionary that contains the ctags languages as keys, and corresponding special cmds, args, etc. as values.
Commits on Oct 29, 2011
  1. Make list of ignored syntax groups configurable

    authored
    While trying to fix issue #20 I decided to refactor the code that
    handles ignored syntax groups: Previously the list of excluded groups
    was hard coded in two places, now it's a configuration option. Then
    it turned out that including shFunction* in the list of excluded
    syntax groups didn't fix the reported issue...
Commits on Oct 1, 2011
Commits on Sep 17, 2011
Commits on Sep 5, 2011
  1. Improve easytags_dynamic_files implementation (best of both worlds?)

    authored
    Some users want the plug-in to use existing project specific tags files
    but fall back to the global tags file or a file type specific tags file
    if a project specific tags file does not exist. Other users want the
    plug-in to automatically create project specific tags files. Both are
    reasonable options to have. I hope with this change we can all
    be happy :-) (see also issue #15 and issue #16 on GitHub).
Commits on Aug 31, 2011
  1. Make "easytags_dynamic_files" create missing tags files

    authored
    Suggested by Strahinja Marković in GitHub issue #15:
    #15
Commits on Jul 8, 2011
Something went wrong with that request. Please try again.