| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While writing the `easytags.vim` plug-in at one point I added the
following line to my `~/.vimrc` script:
:set tags=~/.vimtags
After publishing the plug-in I totally forgot about the `tags` option
and how the plug-in depends on it for all of its functionality :-S
The plug-in now adds the (possibly user-defined) value of the
`easytags_file` option to Vim's `tags` option, thereby making Vim's
internals aware of the tags file.
Oh by the way, the plug-in is now more-or-less Windows compatible.
The only remaining problems are the flashing command prompt (which
I know how to fix) and the fact that CursorHold seems to fire
repeatedly...
|
| | |
|
| |
|
|
|
|
|
| |
The dynamic syntax highlighting performed by `easytags.vim` depends on
the extra "language" field which Exuberant Ctags can be instructed to
add to tags files with the --fields=+l command-line argument, however
the `:UpdateTags` command didn't add the --fields argument! Now it does.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In my ~/.vimrc I've set the following:
:let c_syntax_for_h = 1
Which means easytags.vim will also scan *.h files as C source-code.
However Exuberant Ctags by default scans *.h files as C++, so when
you update your global tags file as follows from the command-line:
ctags -af ~/.vimtags /usr/include/lua5.1/*.h
Which I happened to try today, the new tags won't be highlighted in
your C source-code because Exuberant Ctags thinks it's C++ and Vim
doesn't know otherwise. I've now added support for aliases between
file types and added a default set of aliases between C, C++, Obj-C
and Obj-C++.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While writing a LaTeX document I found out that Exuberant Ctags was
corrupting my tags file by writing invalid entries. Because half my
self-developed Vim plug-ins deal with Exuberant Ctags integration
which I use constantly this broke my whole environment :-)
Since the main point of easytags.vim is to fully automate tags
generation, corrupt files that need to be repaired by hand are
unacceptable. Therefor I've added an option to enable ignoring selected
file types and defined the default to exclude `*.tex` files.
If you disagree with me, feel free to set the option
`easytags_ignored_filetypes` to an empty string,
in which case no file types will be ignored.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The plug-in used an inconsistent mix of error handling using both :throw and
:echoerr. The public facing functions have now been wrapped in try/catch blocks
and all internal functions :throw error message strings.
|
| |
|
|
|
|
| |
On the one hand I don't want to force people to download half my Vim profile
before they can try one of the plug-ins I've written, but on the other hand I
don't want to keep copy/pasting miscellaneous functions all over the place...
|
| | |
|
| |
|
