aboutsummaryrefslogtreecommitdiffstats
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Improve documentation of `easytags_dynamic_files' optionPeter Odding2015-04-141-2/+7
| | | | | | See also issue 92 and issue 116 on GitHub: - https://github.com/xolox/vim-easytags/issues/92 - https://github.com/xolox/vim-easytags/issues/116
* Merge pull request #117: Fix typo in READMEPeter Odding2015-04-141-3/+4
|\
| * Typo fixJrean2015-04-141-2/+2
|/
* Improve easytags_auto_{update,highlight} option documentationPeter Odding2015-04-021-0/+6
| | | | | | | | | | | | | Try to prevent confusion like in issue #92 on GitHub by @oryband: I had to comment out the auto_update/highlight lines in order for easytags to create the local .tags file. I thought that these options were meant only for on_cursorhold. The documentation regarding this is quite ambiguous: If on_cursorhold is off, why does auto_update/highlight also apply to events? Events aren't auto - I set them manually. For details: https://github.com/xolox/vim-easytags/issues/92
* Refer from easytags_always_enabled to easytags_async in README.mdPeter Odding2015-04-021-2/+2
|
* Update installation instructionsPeter Odding2015-04-021-40/+25
|
* Merge pull request #111: Give precedence to dynamic files over storage by ↵Peter Odding2015-03-151-1/+1
| | | | | | | | | | | | | | | | | | | 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: https://github.com/xolox/vim-easytags/pull/111 Which came forth from issue 102: https://github.com/xolox/vim-easytags/issues/102
* Add missing link to README (issue #98)Peter Odding2014-11-211-20/+21
|
* Improve handling & docs of g:easytags_opts option (issue #98)Peter Odding2014-11-211-1/+8
|
* Add g:easytags_opts option (issue #98)Peter Odding2014-11-131-17/+27
| | | | | See also issue #98 on GitHub: https://github.com/xolox/vim-easytags/issues/98
* Support for Perl highlighting (thanks to Jessica Kathleen McIntosh, see ↵Peter Odding2014-09-171-5/+6
| | | | | | | issue #97) See issue #97 on GitHub: https://github.com/xolox/vim-easytags/issues/97
* Add g:easytags_suppress_report optionblukat292014-08-241-0/+9
|
* Use timers to identify slow[est] parts of vim-easytagsPeter Odding2014-07-191-12/+30
| | | | | | | 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!
* Support for keyword based syntax highlighting (much faster)Peter Odding2014-07-091-14/+41
| | | | | | | | | | | 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-081-1/+4
|
* Merge pull request #84: Asynchronous tags file updates! \o/Peter Odding2014-07-081-36/+34
|\ | | | | | | | | | | | | | | | | | | | | 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
| * Support for synchronous + asynchronous tags file updates (huge refactoring)Peter Odding2014-06-221-36/+30
|/ | | | | 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-161-1/+1
|
* Make sure vim-misc is installed, politely complain if it isn'tPeter Odding2013-08-191-1/+1
|
* Merge pull request #59: Java interfaces supportPeter Odding2013-07-161-1/+1
| | | | | See pull request #59 on GitHub: https://github.com/xolox/vim-easytags/pull/59
* Improve handling of ignored syntax groups (issue #57)Peter Odding2013-06-201-8/+0
|
* Bug fix: Don't highlight C tags inside #if 0 (issue #57)Peter Odding2013-06-171-218/+215
| | | | | | | | | $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-251-30/+43
| | | | from now on)
* Remove compatibility checking of miscellaneous scriptsPeter Odding2013-05-231-2/+2
|
* Document the g:easytags_events option (issue #46)Peter Odding2013-05-201-12/+31
| | | | | Issue #46 on GitHub: https://github.com/xolox/vim-easytags/issues/46
* Document BufWritePost example, improve documentation structure (issue #46)Peter Odding2013-05-191-27/+50
| | | | | Issue #46 on GitHub: https://github.com/xolox/vim-easytags/issues/46
* Add g:easytags_updatetime_warn option, improve documentation (issue #47)Peter Odding2013-05-191-18/+45
| | | | | Issue #47 on GitHub: https://github.com/xolox/vim-easytags/issues/47
* Bug fix: Don't complain about 'updatetime' when autoload is disabled (issue #47)Peter Odding2013-05-191-2/+2
| | | | | Issue #47 on GitHub: https://github.com/xolox/vim-easytags/issues/47
* Don't try to use dynamic tags files for non-writable directories (issue #29)Peter Odding2013-04-301-2/+3
| | | | | This fixes the problem described here: https://github.com/xolox/vim-easytags/issues/29
* Merge pull request #36Peter Odding2013-04-211-1/+1
|\
* | Workaround low 'updatetime' intelligentlyPeter Odding2013-04-191-37/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 :-)
* | Move g:easytags_languages documentation to README.mdPeter Odding2013-04-191-45/+48
| | | | | | | | | | Integration of pull request #40: https://github.com/xolox/vim-easytags/pull/40
* | Merge branch 'enh-languages' of git://github.com/inkarkat/vim-easytags into ↵Peter Odding2013-04-191-0/+27
|\ \ | | | | | | | | | inkarkat-enh-languages
| * | ENH: Allow to specify different ctags tool for particular languages.Ingo Karkat2013-03-071-0/+27
| |/ | | | | | | 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.
* / Bug fix for highlighting of function names in shell scriptsPeter Odding2013-04-181-0/+44
|/
* Make list of ignored syntax groups configurablePeter Odding2011-10-291-0/+6
| | | | | | | | 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...
* Bump version + minor updates for Awk, Shell & TCL supportPeter Odding2011-10-011-11/+19
|
* New g:easytags_updatetime_autodisable option (issue #17, reported by ↵Peter Odding2011-09-171-15/+36
| | | | Strahinja Marković)
* Improve easytags_dynamic_files implementation (best of both worlds?)Peter Odding2011-09-051-12/+18
| | | | | | | | | 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).
* Make "easytags_dynamic_files" create missing tags filesPeter Odding2011-08-311-13/+9
| | | | | Suggested by Strahinja Marković in GitHub issue #15: https://github.com/xolox/vim-easytags/issues/15
* Explain how to setup custom ctags command line optionsPeter Odding2011-07-091-6/+18
|
* Fix broken link in READMEPeter Odding2011-06-271-2/+2
|
* Support buffer local variants of most optionsPeter Odding2011-06-271-17/+21
|
* Add easytags_auto_update/auto_highlight optionsPeter Odding2011-06-261-0/+28
|
* Allow enabling both dynamic and file type tags filesKenny Stuart2011-06-241-0/+9
| | | | | | | | When both options are enabled, project specific tags files take precedence if they exist and are writable, otherwise a file type tags file is used. (Stuart wrote this code, Peter added the check for supported file types)
* Remove duplicate tag from Vim help filePeter Odding2011-06-171-2/+1
|
* Documentation bug fix (it's getting late..)Peter Odding2011-06-141-1/+1
|
* 2x faster syntax highlighting using Python Interface to Vim :-)Peter Odding2011-06-141-7/+37
|
* :TagsByFileType to create filetype specific tagsfiles from global tagsfilePeter Odding2011-06-131-0/+4
|
* Basic support for file type specific tags files!Peter Odding2011-06-131-0/+12
|