| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
See also pull request #49 for my previous and failed attempt:
https://github.com/xolox/vim-easytags/pull/49
|
| |
|
|
|
|
|
| |
See also issue #58 on GitHub:
https://github.com/xolox/vim-easytags/issues/58
|
| |
|
|
|
|
|
| |
See issue #57 on GitHub:
https://github.com/xolox/vim-easytags/issues/57
|
|
|
|
|
|
|
|
|
| |
$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
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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...
|
| |
|
| |
|
| |
|
|
|
|
| |
Haugwitz)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Bug fix: :UpdateTags! didn't work because of a typo
|
| |
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* The easytags plug-in caches known tagged files so it doesn't have to
run :UpdateTags whenever you edit an existing file. The previous
implementation was based on the assumption of one global tags file so
wasn't compatible with the concept of file type specific tags files.
This should now be fixed.
* Previously the plug-in worked with a combination of parsed and
unparsed tags file entries which made the code confusing. I've now
cleaned this up so that the plug-in only keeps one type of data in
memory.
* Moved resetting of s:cached_filenames from the end to the start of the
functions that call s:canonicalize() to avoid caching invalid data.
PS. I've benchmarked two cache_tagged_files() implementations, one using
taglist('.'), the other calling xolox#easytags#read_tagsfile() on each
tags file reported by the tagfiles() function. It turns out that
taglist('.') is very slow, which explains why I went with the code
that calls xolox#easytags#read_tagsfile() in a loop.
|
| |
|
| |
|
| |
|
|
|
|
| |
(in preparation for file type specific tags files)
|
|
|
|
| |
The plug-in now checks if dynamic tags files are writable.
|
|
|
|
|
|
|
|
|
|
|
| |
The new events are FocusGained, ShellCmdPost and ShellFilterPost but
they're only used when g:easytags_always_enabled is enabled (it's
disabled by default).
Users can now define their own list of preferred events to override the
defaults by setting the new g:easytags_events option to a list of event
names. I haven't documented the new option yet because I'm not convinced
it's an improvement in terms of usability over the old situation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Daniel Hahler pointed out to me that the feedkeys() hack is no longer
needed since Vim 7.3. Now it will only be used for earlier versions.
|
|
|
|
|
|
|
|
| |
Because s:RegisterTagsFile() is (supposed to be) idempotent we can just
call it twice instead of relying on users to properly configure the
plug-in. See the discussion on the previous commit* for more information.
* http://github.com/xolox/vim-easytags/commit/3466f61
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default the plug-in initializes the &tags option as soon as possible
so that the global tags file is available when using "vim -t some_tag".
If you don't use "vim -t" and want to defer registering the global tags
file until the interface has been initialized you can now set the global
variable g:easytags_register_late = 1.
This commit is based on a pull request from Daniel Hahler, I added the
option to enable either mode of initialization (I guess Daniel doesn't
use "vim -t some_tag", but I certainly do :-). Here's the original
commit message:
Move calling RegisterTagsFile to `au VimEnter`.
Calling RegisterTagsFile on VimEnter instead of when including the
plugin appears to make it behave better when (re)setting 'tags' in
vimrc.
I do not remember if this is related to using tplugin only.
|
|
|
|
| |
While it does no harm, it is not necessary.
|
|
|
|
|
|
|
|
|
|
|
| |
'Development' is being used when ctags is getting built from its source
repository. This is what it looks like:
% ctags --version
Exuberant Ctags Development, Copyright (C) 1996-2009 Darren Hiebert
Compiled: Mar 8 2011, 17:57:10
Addresses: <dhiebert@users.sourceforge.net>, http://ctags.sourceforge.net
Optional compiled features: +win32, +regex, +internal-sort
|
|
|
|
| |
When set and != 0 this will suppress the ctags warning on startup.
|
|
Let's hope this works the first time...
(never used git submodules before)
|