| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
|\ |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
| |
See also issue #98 on GitHub:
https://github.com/xolox/vim-easytags/issues/98
|
|
|
|
|
|
|
| |
issue #97)
See issue #97 on GitHub:
https://github.com/xolox/vim-easytags/issues/97
|
| |
|
|
|
|
|
|
|
| |
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!
|
|
|
|
|
|
|
|
|
|
|
| |
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 :-).
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
| |
See also pull request #49 for my previous and failed attempt:
https://github.com/xolox/vim-easytags/pull/49
|
| |
|
| |
|
|
|
|
|
| |
See pull request #59 on GitHub:
https://github.com/xolox/vim-easytags/pull/59
|
| |
|
|
|
|
|
|
|
|
|
| |
$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
|
|
|
|
| |
from now on)
|
| |
|
|
|
|
|
| |
Issue #46 on GitHub:
https://github.com/xolox/vim-easytags/issues/46
|
|
|
|
|
| |
Issue #46 on GitHub:
https://github.com/xolox/vim-easytags/issues/46
|
|
|
|
|
| |
Issue #47 on GitHub:
https://github.com/xolox/vim-easytags/issues/47
|
|
|
|
|
| |
Issue #47 on GitHub:
https://github.com/xolox/vim-easytags/issues/47
|
|
|
|
|
| |
This fixes the problem described here:
https://github.com/xolox/vim-easytags/issues/29
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 :-)
|
| |
| |
| |
| |
| | |
Integration of pull request #40:
https://github.com/xolox/vim-easytags/pull/40
|
|\ \
| | |
| | |
| | | |
inkarkat-enh-languages
|
| |/
| |
| |
| | |
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.
|
|/ |
|
|
|
|
|
|
|
|
| |
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...
|
| |
|
|
|
|
| |
Strahinja Marković)
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
Suggested by Strahinja Marković in GitHub issue #15:
https://github.com/xolox/vim-easytags/issues/15
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
| |
|
| |
|
| |
|