aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Improve Perl function tag highlighting (more accurate now)Peter Odding2014-11-031-3/+3
| | | | | As suggested in issue #97, for details see: https://github.com/xolox/vim-easytags/issues/97
* Bug fix for xolox#easytags#filetypes#find_ctags_aliases()Peter Odding2014-10-212-2/+3
| | | | | | | | When a canonical Vim file type mapped to a group of file types, the group was returned without the canonical file type :-s See also issue #91 on GitHub: https://github.com/xolox/vim-easytags/issues/91
* Bug fix for xolox#easytags#define_tagkind() invocationsPeter Odding2014-10-211-8/+10
| | | | | | | | | | | It should be given a canonical file type and since I just changed the canonical file type for C to be C++ the invocations should be updated as well. This should really have been part of the change set with id 9b6e7d125c660f31091f59b52de9b1e425cbcb64. That's what I get for not testing properly... See also issue #91 on GitHub: https://github.com/xolox/vim-easytags/issues/91
* Make xolox#easytags#filetypes#add_group() easier to understandPeter Odding2014-10-211-4/+5
|
* Change file type canonicalization to treat C as C++Peter Odding2014-10-202-5/+19
| | | | | | | | | | | | Please refer to the inline comments for more details. This will hopefully fix issue #91 on GitHub: https://github.com/xolox/vim-easytags/issues/91 PS. I've completely removed the objc/objcpp grouping because I don't know these languages so I don't know what grouping would be correct anyway. Until a user with an informed opinion chimes in it's better to just remove this grouping.
* Support for Perl highlighting (thanks to Jessica Kathleen McIntosh, see ↵Peter Odding2014-09-173-9/+21
| | | | | | | issue #97) See issue #97 on GitHub: https://github.com/xolox/vim-easytags/issues/97
* Merge pull request #95: Add g:easytags_suppress_report optionPeter Odding2014-09-143-14/+31
|\
| * Add g:easytags_suppress_report optionblukat292014-08-243-5/+24
|/
* Bug fix for issue #90 caused by pull request #84 (async refactor)Peter Odding2014-08-082-3/+8
| | | | | | | | See issue 90 on GitHub: https://github.com/xolox/vim-easytags/issues/90 This was caused by the async refactor: https://github.com/xolox/vim-easytags/pull/84
* Make it easier to debug tag file selectionPeter Odding2014-08-081-1/+10
|
* Use timers to identify slow[est] parts of vim-easytagsPeter Odding2014-07-193-21/+85
| | | | | | | See also https://github.com/xolox/vim-easytags/pull/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!
* Bug fix: Restore default syntax pattern prefix/suffix (word boundaries)Peter Odding2014-07-091-5/+9
| | | | | | | | | | This is a bug fix / improvement to the new syntax keyword usage introduced in b6f8757d004d5f4ef7280fd111a21821e6bee79a. Also relevant is issue #68 on GitHub, see https://github.com/xolox/vim-easytags/issues/68 @tarmack: Thanks for the feedback earlier today, it's now fixed! :-)
* Filter out forbidden syntax keyword argumentsPeter Odding2014-07-091-2/+25
| | | | | | | | This is a bug fix / improvement to the new syntax keyword usage introduced in b6f8757d004d5f4ef7280fd111a21821e6bee79a. Also relevant is issue #68 on GitHub, see https://github.com/xolox/vim-easytags/issues/68
* Deduplicate syntax keyword argumentsPeter Odding2014-07-091-4/+4
| | | | | | | | This is a bug fix / improvement to the new syntax keyword usage introduced in b6f8757d004d5f4ef7280fd111a21821e6bee79a. Also relevant is issue #68 on GitHub, see https://github.com/xolox/vim-easytags/issues/68
* Support for keyword based syntax highlighting (much faster)Peter Odding2014-07-093-31/+104
| | | | | | | | | | | See the following issues on GitHub: - https://github.com/xolox/vim-easytags/issues/68 - https://github.com/xolox/vim-easytags/pull/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 :-).
* Credit Ingo for his work, thank other contributors as wellPeter Odding2014-07-082-3/+8
|
* Merge pull request #84: Asynchronous tags file updates! \o/Peter Odding2014-07-087-565/+589
|\ | | | | | | | | | | | | | | | | | | | | This is part 1/2 of speeding up the vim-easytags plug-in. Refer to the pull request for details: https://github.com/xolox/vim-easytags/pull/84 In part 2/2 I want to speed up the dynamic syntax highlighting. Potentially related open issues on GitHub (probably missed a few): - https://github.com/xolox/vim-easytags/issues/32 - https://github.com/xolox/vim-easytags/issues/41 - https://github.com/xolox/vim-easytags/issues/68
| * Bug fix for typo introduced in 6c7a66349ecPeter Odding2014-07-011-2/+2
| |
| * Automatically create missing directories when writing tags filesPeter Odding2014-06-301-0/+5
| |
| * Refactor atomic file updates into a feature of vim-miscPeter Odding2014-06-301-3/+4
| |
| * Bug fix for Vim based syntax highlighting of tagsPeter Odding2014-06-301-2/+2
| |
| * Actually enable the automatic commands introduced in 6c7a66349ec :-)Peter Odding2014-06-291-2/+2
| |
| * Bug fix for invalid tags filtering (cache.exists() was broken, now fixed)Peter Odding2014-06-291-5/+11
| |
| * Merge pull request #87: Avoid error about empty Dictionary keyPeter Odding2014-06-291-4/+7
| |\
| | * FIX: Avoid error about empty Dictionary key.Ingo Karkat2014-06-231-0/+3
| | | | | | | | | | | | I had a degenerate tags file that had *two* tabs separating the tag from the filespec column; parsing that yields an empty filespec, which caused E713. There used to be an explicit check for that; with your recent refactorings, one instance of that check was lost. Here it is again!
| * | Merge pull request #86: Ensure full absolute tagsfile filespec in async modePeter Odding2014-06-291-1/+1
| |\ \
| | * | FIX: Ensure full absolute tagsfile filespec in async mode.Ingo Karkat2014-06-231-1/+1
| | |/ | | | | | | | | | On Windows, tagfiles() can return a filespec that is absolute to the current drive (i.e. \foo\bar\tags). In async mode, the forked Vim process may have another current drive, so it should be ensured that the filespec is a full one, including the drive letter: D:\foo\bar\tags.
| * | Don't use :redraw in :HighlightTags during session loadingPeter Odding2014-06-291-1/+5
| | |
| * | Disable automatic tags file updates during session loadingPeter Odding2014-06-291-1/+6
| | |
| * | Disable automatic tags file updates during :vimgrepPeter Odding2014-06-292-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | This change is related to pull request #83 however that pull request wasn't merged here (and won't be merged at all) because it was based on the old/dead `async-cleanup' feature branch (see pull request #49 on GitHub) instead of the new `async-take-two' feature branch (see pull request #84 on GitHub). This change set implements the equivalent on the new feature branch (without introducing another option).
| * | Silence asynchronous tags file updates by defaultPeter Odding2014-06-291-3/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is related to pull request #82 however that pull request wasn't merged here (and won't be merged at all) because it was based on the old/dead `async-cleanup' feature branch (see pull request #49 on GitHub) instead of the new `async-take-two' feature branch (see pull request #84 on GitHub). This change set implements the equivalent on the new feature branch. In addition to Ingo's comments in pull request #82, the asynchronous message frequently disturbs me while typing a Vim command, which is kind of annoying. If everything goes well and we can get the async mode to be stable enough to become the default mode then the status messages will only be interesting when debugging a problem anyway.
| * Support for synchronous + asynchronous tags file updates (huge refactoring)Peter Odding2014-06-227-562/+537
|/ | | | | See also pull request #49 for my previous and failed attempt: https://github.com/xolox/vim-easytags/pull/49
* Merge pull request #78: Bug fix for accelerated highlighting using PythonPeter Odding2014-06-164-7/+7
|\
| * Replace \0 by \g<0> in python submat tso2014-03-091-2/+2
|/ | | | | | | | | | | | | | | | | | > The back reference \g<0> substitutes in the entire substring > matched by the RE. > http://docs.python.org/2/library/re.html#re.sub The documentation does not mention \0 as an alias to it. Although \1 to \9 works. I guess this alias (\0 <=> \g<0>) existed in old python version, but it is not the case any more. In python 2.7 and 3.3: > import re; re.compile(r'123').sub(r'@\0@',"ab123cd") 'ab@\x00@cd' # KO > import re; re.compile(r'123').sub(r'@\g<0>@',"ab123cd") 'ab@123@cd' # OK
* Bug fix: Support for disabled languages in Exuberant Ctags (issue #62)Peter Odding2013-09-011-11/+13
| | | | | See issue #62 on GitHub: https://github.com/xolox/vim-easytags/issues/62
* Merge pull request #63: fix 'multiple repeat' error from regex for c++ filetypesPeter Odding2013-08-312-4/+4
|\ | | | | | | | | See pull request #63 on GitHub: https://github.com/xolox/vim-easytags/pull/63
| * fix 'multiple repeat' error from regex for c++ filetypesJulian Taylor2013-08-271-1/+1
|/ | | | | | unescaped ++ is invalid regex causing easytag to fall back to the vimscript highlighting which does not split the regex into small chunks that vim can handle.
* Make sure vim-misc is installed, politely complain if it isn'tPeter Odding2013-08-193-4/+18
|
* Merge pull request #59: Java interfaces supportPeter Odding2013-07-163-4/+10
|\ | | | | | | | | See pull request #59 on GitHub: https://github.com/xolox/vim-easytags/pull/59
| * add highlighting for java interfaces. tested with ctags-5.8Nir Atias2013-07-101-0/+6
|/
* Make Exuberant Ctags discovery (version checking) verbose (easier to debug)Peter Odding2013-06-222-18/+30
| | | | | See also issue #58 on GitHub: https://github.com/xolox/vim-easytags/issues/58
* Bug fix for :UpdateTags: Gracefully handle case where no supported file type ↵Peter Odding2013-06-221-2/+2
| | | | | | | is known See the comment by @ixti in issue #57 on GitHub: https://github.com/xolox/vim-easytags/issues/57#issuecomment-19720077
* Improve plug-in initialization (make it more robust)Peter Odding2013-06-222-89/+94
| | | | | See also issue #58 on GitHub: https://github.com/xolox/vim-easytags/issues/58
* Improve handling of ignored syntax groups (issue #57)Peter Odding2013-06-204-19/+33
|
* Bug fix: Don't highlight C tags inside #if 0 and Doxygen comments (issue #57)Peter Odding2013-06-192-4/+4
| | | | | See issue #57 on GitHub: https://github.com/xolox/vim-easytags/issues/57
* Bug fix: Don't highlight C tags inside #if 0 (issue #57)Peter Odding2013-06-173-222/+219
| | | | | | | | | $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: https://github.com/xolox/vim-easytags/issues/57
* Document vim-misc as external dependency (needs to be installed separately ↵Peter Odding2013-05-254-36/+70
| | | | from now on)
* Merge branch 'master' into devPeter Odding2013-05-250-0/+0
|\
| * Release 3.3.5Peter Odding2013-05-2313-78/+1234
|/
* Cleaned up old miscellaneous scriptsPeter Odding2013-05-2312-1112/+0
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 18:21:47 +0000