aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Remove compatibility checking of miscellaneous scriptsPeter Odding2013-05-232-6/+4
|
* Updated miscellaneous scriptsPeter Odding2013-05-205-16/+46
|\
| * Update documentation in READMEPeter Odding2013-05-201-9/+36
| |
| * Add xolox#misc#os#find_vim() functionPeter Odding2013-05-202-3/+32
| |
| * Remove line continuation from xolox#misc#os scriptPeter Odding2013-05-201-3/+1
| |
| * Add xolox#misc#timer#force() functionPeter Odding2013-05-203-9/+12
| |
* | Document the g:easytags_events option (issue #46)Peter Odding2013-05-202-13/+42
| | | | | | | | | | Issue #46 on GitHub: https://github.com/xolox/vim-easytags/issues/46
* | Updated miscellaneous scriptsPeter Odding2013-05-2013-141/+356
|\|
| * Improve the error message thrown by xolox#misc#compat#check()Peter Odding2013-05-201-10/+15
| |
| * Added inline documentation everywhere, also included in README.md*Peter Odding2013-05-1913-104/+688
| | | | | | | | | | | | | | * Using a new tool I'm working on: A Python script that scans a Vim script project for global function definitions and their documentation comments (in Markdown format) and generates a single Markdown document that provides an overview of the functions defined in the scripts.
| * Bug fix: Correct wrong expansion order in xolox#misc#path#which()Peter Odding2013-05-192-17/+14
| |
| * Improve error reporting in xolox#misc#os#exec()Peter Odding2013-05-192-8/+18
| |
| * Bug fix: Make xolox#misc#os#exec() compatible with (t)csh (reported by Armin ↵Peter Odding2013-05-192-4/+12
| | | | | | | | | | | | | | Widegreen) Original report: https://github.com/xolox/vim-easytags/pull/48
| * Apply hard wrapping to README.mdPeter Odding2013-05-191-25/+68
| |
| * Bug fix for xolox#misc#option#eval_tags() optionPeter Odding2013-05-191-2/+2
| |
| * Improve reporting of multi-line messages (now split over lines)Peter Odding2013-05-191-2/+5
| |
* | Document BufWritePost example, improve documentation structure (issue #46)Peter Odding2013-05-192-36/+71
| | | | | | | | | | 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-193-23/+65
| | | | | | | | | | 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-192-27/+28
| | | | | | | | | | Issue #47 on GitHub: https://github.com/xolox/vim-easytags/issues/47
* | Updated miscellaneous scriptsPeter Odding2013-05-134-68/+128
|\|
| * Make xolox#misc#os#exec() report exit codes (breaks backwards compatibility)Peter Odding2013-05-132-18/+106
| | | | | | | | Working towards fixing this issue: xolox/vim-lua-ftplugin#8
* | Support for composed file types (issue #28)Peter Odding2013-05-051-9/+24
| | | | | | | | | | | | | | Issue #28 on GitHub: problem with composed file types https://github.com/xolox/vim-easytags/issues/28
* | Don't try to use dynamic tags files for non-writable directories (issue #29)Peter Odding2013-04-303-4/+12
| | | | | | | | | | This fixes the problem described here: https://github.com/xolox/vim-easytags/issues/29
* | Updated miscellaneous scriptsPeter Odding2013-04-303-22/+53
|\|
| * Improve the xolox#misc#path#* functionsPeter Odding2013-04-282-19/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - xolox#misc#path#absolute() was completely rewritten. It no longer uses fnamemodify() which doesn't work on non-existing pathnames. It's now written on top of xolox#misc#path#split() and xolox#misc#path#join(). It should now properly normalize directory separators as suggested in this pull request: xolox/vim-session#29 - xolox#misc#path#split() and xolox#misc#path#join() were enhanced with proper handling of UNC paths and respect for the 'shellslash' option on Windows (tested on Windows XP SP2, the only Windows I have available)
* | Updated miscellaneous scriptsPeter Odding2013-04-283-81/+28
|\|
| * Change the repository layout to that of a proper Vim plug-inPeter Odding2013-04-2813-40/+55
| |
* | Merge pull request #37 (prevent cache corruption by moving before tags write)Peter Odding2013-04-211-5/+8
|\ \
| * | FIX: Prevent cache corruption by moving before tags write.Ingo Karkat2012-11-261-4/+6
| | | | | | | | | | | | | | | | | | A side effect of xolox#easytags#write_tagsfile() is that the entries argument is joined together. This then causes problems in s:cache_tagged_files_in(), where the filename element is addressed via entry[1]. When the entries have been flattened, this accesses a single character, and then the cache is corrupted. To fix this, move the cache update before the writing of the tags file. This avoids the need to make a copy of the entries before flattening them.
* | | Bug fix for E688: More targets than List itemsPeter Odding2013-04-211-2/+2
| | |
* | | Merge pull request #36Peter Odding2013-04-213-5/+5
|\ \ \
| * | | Do not highlight tags on :UpdateTags when it is configured off.Ingo Karkat2012-10-221-1/+1
| |/ / | | | | | | | | | I turn off highlighting of tags (:let g:easytags_auto_highlight = 0), because I usually have very large tags databases. When I manually trigger an update via :UpdateTags, the highlighting is processed, though, resulting in the long delay or "regexp too long" error. The :UpdateTags command should honor the configuration setting.
* | | Make compatibility with miscellaneous scripts explicitPeter Odding2013-04-205-22/+93
|\ \ \ | | |/ | |/|
| * | Make backwards compatibility explicitPeter Odding2013-04-202-0/+25
| | |
| * | Explain in README.md why vim-misc is what it is (issue #1)Peter Odding2013-04-201-3/+26
| | |
| * | Improve xolox#misc#buffer#prepare()Peter Odding2013-04-182-15/+29
| | |
| * | Bug fix: Encode ":" on Mac OS X in xolox#misc#path#encode()Peter Odding2013-04-181-2/+9
| | | | | | | | | | | | Reported here: https://github.com/xolox/vim-notes/pull/28
* | | Add `ctags-exuberant' to the list of program names (closes issue #39)Peter Odding2013-04-192-5/+6
| | |
* | | Workaround low 'updatetime' intelligentlyPeter Odding2013-04-193-52/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-193-46/+70
| | | | | | | | | | | | | | | 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-192-27/+76
|\ \ \ | | | | | | | | | | | | inkarkat-enh-languages
| * | | ENH: Allow to specify different ctags tool for particular languages.Ingo Karkat2013-03-072-27/+76
| | |/ | |/| | | | | | | 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.
* | | Minor changes to pull request #43 on GitHub (thank you Ingo :-)Peter Odding2013-04-191-34/+40
| | | | | | | | | | | | The pull request: https://github.com/xolox/vim-easytags/pull/43
* | | Merge branch 'enh-fingerprint-avoids-update' of ↵Peter Odding2013-04-181-2/+40
|\ \ \ | | | | | | | | | | | | git://github.com/inkarkat/vim-easytags into inkarkat-enh-fingerprint-avoids-update
| * | | BUG: Avoid E713 when attempting fingerprinting without current file.Ingo Karkat2013-04-171-0/+5
| | | | | | | | | | | | | | | | When creating a tags file for an entire directory, the a:cfile variable is empty. In that case, the cache doesn't work. Avoid "E713: Cannot use empty key for Dictionary" by checking for that.
| * | | ENH: Avoid tag updating when ctags output has identical fingerprint.Ingo Karkat2013-03-281-2/+35
| |/ / | | | | | | | | | | | | We can avoid the lengthy and blocking update of the tags database when the ctags output returns the same information as before; i.e. nothing tag-relevant has been changed since the last update. Since 7.3.816, Vim has a sha256() function that allows us to quickly calculate a fingerprint over the ctags output. When that is not available, only handle the special case of a (covered) file that has no tags at all (as calculating a hash in Vimscript is costly and would probably defeat the intended speedup).
* | | Add .gitignore file and ignore doc/tags (closes issue #15)Peter Odding2013-04-181-0/+1
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 16:25:25 +0000