| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* In response to issue 5 [1] I've changed the git submodule config to
references GitHub using HTTPS instead of the git protocol, this
should make it easier for people behind firewalls to clone the
repository.
* In response to an issue [2] reported against one of my other Vim
plug-ins I've changed the link to the ZIP archive to include the
".zip" extension. The old links without extensions will keep working
so as not to break links in older README files.
* The link with the text "CTRL-]" broke some Markdown implementations
so I changed the text to use an HTML entity instead of a plain "]".
[1] https://github.com/xolox/vim-easytags/issues/5
[2] https://github.com/xolox/vim-session/issues/5
|
|
|
|
|
| |
This is a generated file which I normally wouldn't commit but
Pathogen users like to check out the git repository directly.
|
|
|
|
|
|
|
|
|
|
|
| |
'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)
|
| |
|
| |
|
| |
|
|
|
|
| |
This improves accuracy because PHP doesn't have first class functions
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The easytags#update() function previously used the variable argument
list notation `...' but I just found out [the hard way] that this only
supports up to 20 arguments. Therefor I've now changed easytags#update()
to receive a list of zero or more filenames as its third argument.
|
|
|
|
| |
See http://github.com/xolox/vim-publish/commit/be98f4328bb631cd4c67d8951ff7c413b7cb6355
|
| |
|
| |
|
|
|
|
|
|
|
| |
Dynamic highlighting supports C/C++ function prototypes to enable
highlighting of library functions based on just the headers, but until
now the easytags.vim plug-in didn't request ctags to include function
prototypes. Now it does so automatically.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I developed (parts of) my shell.vim plug-in after noticing the annoying
command prompt windows that pop up temporarily on Windows when the
easytags plug-in runs ctags. Because the shell.vim plug-in was a proof
of concept I hadn't published any integration between the two plug-ins.
Since then I've had several requests for this so here it is :-)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* The :UpdateTags command now passes any arguments given to it on to
Exuberant Ctags, which sounds simple enough but required a complex
implementation. This means users can now do things like:
:UpdateTags -R ~/.vim
Because Ctags can be run easily from inside Vim, users won't have to
run it manually from the command line. The plug-in also makes sure
the required command-line options to Ctags are always used.
* Fixed a problem most users will probably never encounter. I'm not
sure whether this is by design or an implementation detail but it's
possible for the "!_TAG_FILE_SORTED" header to appear after one or
more tags and Vim will apparently still use the header! For this
reason the easytags#write_tagsfile() function should also recognize
it, otherwise Vim might complain with "E432: Tags file not sorted".
* Always sort tags in easytags#write_tagsfile() (understands foldcase)
* Finally documented the :UpdateTags and :HighlightTags commands.
* The dynamic highlighting can now be disabled for individual buffers,
which can come in handy when the highlighting conflicts with another
plug-in: Just set the 'b:easytags_nohl' variable to any value.
* Removed hard wrapping from README.md because I've recently switched
to a 21" external monitor ;-)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously* I fixed a bug where easytags.vim failed to register the
global tags file created by the plug-in with Vim, because even though
the &tags option was set by the plug-in, Vim would refuse to acknowledge
the new tags file, i.e. tagfiles() == [].
The fix then was to change :let &tags= to :set tags= which apparently
has a different implementation from :let &tags=?! I assumed this fix
would be valid for both Windows and UNIX, but apparently this still
doesn't work on Windows! There we actually have to use feedkeys() to
convince Vim to change the &tags option... What a hack! :-(
BTW I also fixed an embarrassing typo in the initialization code.
* Bug fix for strange "E433: No tags file" problem:
http://github.com/xolox/vim-easytags/commit/4fef0c17749e687d670b2e9e4e429022ec4c1055
|