Skip to content

Commit 7916b46

Browse files
committed
Document vim-misc as external dependency (needs to be installed separately from now on)
1 parent cbe8cc8 commit 7916b46

File tree

4 files changed

+70
-36
lines changed

4 files changed

+70
-36
lines changed

INSTALL.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,13 @@
1-
If you're looking for the simplest way to get the plug-in up and running, download [the latest ZIP archive](http://peterodding.com/code/vim/downloads/easytags.zip) from [Vim Online](http://www.vim.org/scripts/script.php?script_id=3114), unzip that in `~/.vim/` (on UNIX) or `%USERPROFILE%\vimfiles` (on Windows) and you're good to go.
1+
*Please note that the vim-easytags plug-in requires my vim-misc plug-in which is separately distributed.*
22

3-
If you're using git and/or [Pathogen](http://www.vim.org/scripts/script.php?script_id=2332), [Vundle](https://github.com/gmarik/vundle) or a similar plug-in manager and want to keep the plug-in up to date using git, you can use the GitHub repository directly, it should just work.
3+
Unzip the most recent ZIP archives of the [vim-easytags] [download-easytags] and [vim-misc] [download-misc] plug-ins inside your Vim profile directory (usually this is `~/.vim` on UNIX and `%USERPROFILE%\vimfiles` on Windows), restart Vim and execute the command `:helptags ~/.vim/doc` (use `:helptags ~\vimfiles\doc` instead on Windows). To get started execute `:Note` or `:edit note:`, this will start a new note that contains instructions on how to continue from there (and how to use the plug-in in general).
4+
5+
If you prefer you can also use [Pathogen] [pathogen], [Vundle] [vundle] or a similar tool to install & update the [vim-easytags] [github-easytags] and [vim-misc] [github-misc] plug-ins using a local clone of the git repository.
6+
7+
8+
[download-easytags]: http://peterodding.com/code/vim/downloads/easytags.zip
9+
[download-misc]: http://peterodding.com/code/vim/downloads/misc.zip
10+
[github-easytags]: http://github.com/xolox/vim-easytags
11+
[github-misc]: http://github.com/xolox/vim-misc
12+
[pathogen]: http://www.vim.org/scripts/script.php?script_id=2332
13+
[vundle]: https://github.com/gmarik/vundle

README.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,13 @@ There's just one problem: You have to manually keep your tags files up-to-date a
88

99
## Installation
1010

11-
Unzip the most recent [ZIP archive] [download] file inside your Vim profile directory (usually this is `~/.vim` on UNIX and `%USERPROFILE%\vimfiles` on Windows), restart Vim and execute the command `:helptags ~/.vim/doc` (use `:helptags ~\vimfiles\doc` instead on Windows). Now try it out: Edit any file type supported by Exuberant Ctags and within ten seconds the plug-in should create/update your tags file (`~/.vimtags` on UNIX, `~/_vimtags` on Windows) with the tags defined in the file you just edited! This means that whatever file you're editing in Vim (as long as it's on the local file system), tags will always be available by the time you need them!
11+
*Please note that the vim-easytags plug-in requires my vim-misc plug-in which is separately distributed.*
12+
13+
Unzip the most recent ZIP archives of the [vim-easytags] [download-easytags] and [vim-misc] [download-misc] plug-ins inside your Vim profile directory (usually this is `~/.vim` on UNIX and `%USERPROFILE%\vimfiles` on Windows), restart Vim and execute the command `:helptags ~/.vim/doc` (use `:helptags ~\vimfiles\doc` instead on Windows).
14+
15+
If you prefer you can also use [Pathogen] [pathogen], [Vundle] [vundle] or a similar tool to install & update the [vim-easytags] [github-easytags] and [vim-misc] [github-misc] plug-ins using a local clone of the git repository.
16+
17+
Now try it out: Edit any file type supported by Exuberant Ctags and within ten seconds the plug-in should create/update your tags file (`~/.vimtags` on UNIX, `~/_vimtags` on Windows) with the tags defined in the file you just edited! This means that whatever file you're editing in Vim (as long as it's on the local file system), tags will always be available by the time you need them!
1218

1319
Additionally if the file you just opened is an AWK, C#, C, C++, Objective-C, Java, Lua, PHP, Python, Ruby, Shell, Tcl or Vim source file you should also notice that the function and type names defined in the file have been syntax highlighted.
1420

@@ -325,15 +331,19 @@ This software is licensed under the [MIT license](http://en.wikipedia.org/wiki/M
325331
[cursorhold]: http://vimdoc.sourceforge.net/htmldoc/autocmd.html#CursorHold
326332
[cygwin]: http://en.wikipedia.org/wiki/Cygwin
327333
[dll]: http://en.wikipedia.org/wiki/Dynamic-link_library
328-
[download]: http://peterodding.com/code/vim/downloads/easytags.zip
334+
[download-easytags]: http://peterodding.com/code/vim/downloads/easytags.zip
335+
[download-misc]: http://peterodding.com/code/vim/downloads/misc.zip
329336
[e339]: http://vimdoc.sourceforge.net/htmldoc/message.html#E339
330337
[exctags]: http://ctags.sourceforge.net/
338+
[github-easytags]: http://github.com/xolox/vim-easytags
339+
[github-misc]: http://github.com/xolox/vim-misc
331340
[hlinks]: http://en.wikipedia.org/wiki/Hard_link
332341
[ide]: http://en.wikipedia.org/wiki/Integrated_development_environment
333342
[jsctags]: https://npmjs.org/package/jsctags
334343
[localtime]: http://vimdoc.sourceforge.net/htmldoc/eval.html#localtime()
335344
[messages]: http://vimdoc.sourceforge.net/htmldoc/message.html#:messages
336345
[neocomplcache]: http://www.vim.org/scripts/script.php?script_id=2620
346+
[pathogen]: http://www.vim.org/scripts/script.php?script_id=2332
337347
[shell]: http://peterodding.com/code/vim/shell/
338348
[slinks]: http://en.wikipedia.org/wiki/Symbolic_link
339349
[syn_groups]: http://vimdoc.sourceforge.net/htmldoc/syntax.html#group-name
@@ -346,3 +356,4 @@ This software is licensed under the [MIT license](http://en.wikipedia.org/wiki/M
346356
[vim_fts]: http://ftp.vim.org/vim/runtime/syntax/
347357
[vim_online]: http://www.vim.org/scripts/script.php?script_id=3114
348358
[vimrc]: http://vimdoc.sourceforge.net/htmldoc/starting.html#vimrc
359+
[vundle]: https://github.com/gmarik/vundle

autoload/xolox/easytags.vim

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
" Vim script
22
" Author: Peter Odding <peter@peterodding.com>
3-
" Last Change: May 23, 2013
3+
" Last Change: May 25, 2013
44
" URL: http://peterodding.com/code/vim/easytags/
55

6-
let g:xolox#easytags#version = '3.3.5'
6+
let g:xolox#easytags#version = '3.3.6'
77

88
" Public interface through (automatic) commands. {{{1
99

doc/easytags.txt

Lines changed: 43 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -73,15 +73,23 @@ see if it would work -- surprisingly well I'm happy to report!
7373
*easytags-installation*
7474
Installation ~
7575

76-
Unzip the most recent ZIP archive [6] file inside your Vim profile directory
77-
(usually this is '~/.vim' on UNIX and '%USERPROFILE%\vimfiles' on Windows),
78-
restart Vim and execute the command ':helptags ~/.vim/doc' (use ':helptags
79-
~\vimfiles\doc' instead on Windows). Now try it out: Edit any file type
80-
supported by Exuberant Ctags and within ten seconds the plug-in should
81-
create/update your tags file ('~/.vimtags' on UNIX, '~/_vimtags' on Windows)
82-
with the tags defined in the file you just edited! This means that whatever
83-
file you're editing in Vim (as long as it's on the local file system), tags
84-
will always be available by the time you need them!
76+
Please note that the vim-easytags plug-in requires my vim-misc plug-in which
77+
is separately distributed.
78+
79+
Unzip the most recent ZIP archives of the vim-easytags [6] and vim-misc [7]
80+
plug-ins inside your Vim profile directory (usually this is '~/.vim' on UNIX
81+
and '%USERPROFILE%\vimfiles' on Windows), restart Vim and execute the command
82+
':helptags ~/.vim/doc' (use ':helptags ~\vimfiles\doc' instead on Windows).
83+
84+
If you prefer you can also use Pathogen [8], Vundle [9] or a similar tool to
85+
install & update the vim-easytags [10] and vim-misc [11] plug-ins using a
86+
local clone of the git repository.
87+
88+
Now try it out: Edit any file type supported by Exuberant Ctags and within ten
89+
seconds the plug-in should create/update your tags file ('~/.vimtags' on UNIX,
90+
'~/_vimtags' on Windows) with the tags defined in the file you just edited!
91+
This means that whatever file you're editing in Vim (as long as it's on the
92+
local file system), tags will always be available by the time you need them!
8593

8694
Additionally if the file you just opened is an AWK, C#, C, C++, Objective-C,
8795
Java, Lua, PHP, Python, Ruby, Shell, Tcl or Vim source file you should also
@@ -105,7 +113,7 @@ A note about Windows ~
105113

106114
On Windows the |system()| function used by 'easytags.vim' causes a command
107115
prompt window to pop up while Exuberant Ctags is executing. If this bothers
108-
you then you can install my shell.vim [7] plug-in which includes a DLL [8]
116+
you then you can install my shell.vim [12] plug-in which includes a DLL [13]
109117
that works around this issue. Once you've installed both plug-ins it should
110118
work out of the box! Please let me know if this doesn't work for you.
111119

@@ -181,8 +189,8 @@ The *g:easytags_languages* option
181189

182190
Exuberant Ctags supports many languages and can be extended via regular
183191
expression patterns, but for some languages separate tools with
184-
ctags-compatible output exist (e.g. jsctags [9] for Javascript). To use these,
185-
the executable and its arguments must be configured:
192+
ctags-compatible output exist (e.g. jsctags [14] for Javascript). To use
193+
these, the executable and its arguments must be configured:
186194
>
187195
let g:easytags_languages = {
188196
\ 'language': {
@@ -417,14 +425,14 @@ your vimrc script, a file type plug-in, etc.):
417425
-------------------------------------------------------------------------------
418426
The *g:easytags_resolve_links* option
419427

420-
UNIX has symbolic links [10] and hard links [11], both of which conflict with
428+
UNIX has symbolic links [15] and hard links [16], both of which conflict with
421429
the concept of having one unique location for every identifier. With regards
422430
to hard links there's not much anyone can do, but because I use symbolic links
423431
quite a lot I've added this option. It's disabled by default since it has a
424432
small performance impact and might not do what unknowing users expect it to:
425433
When you enable this option the plug-in will resolve symbolic links in
426434
pathnames, which means your tags file will only contain entries with canonical
427-
pathnames [12]. To enable this option (which I strongly suggest doing when you
435+
pathnames [17]. To enable this option (which I strongly suggest doing when you
428436
run UNIX and use symbolic links) execute the following Vim command:
429437
>
430438
:let g:easytags_resolve_links = 1
@@ -455,11 +463,11 @@ about this. If you have suggestions, please feel free to submit them.
455463
Passing custom command line arguments to Exuberant Ctags ~
456464

457465
You may want to run Exuberant Ctags with specific command line options, for
458-
example the code_complete [13] plug-in requires the signature field to be
466+
example the code_complete [18] plug-in requires the signature field to be
459467
present. To do this you can create a configuration file for Exuberant Ctags,
460468
e.g. '~/.ctags' on UNIX or '%USERPROFILE%\ctags.cnf' on Windows. The file
461469
should contain one command line option per line. See the Exuberant Ctags
462-
manual [14] for details.
470+
manual [19] for details.
463471

464472
-------------------------------------------------------------------------------
465473
Update & highlight tags immediately after save ~
@@ -633,7 +641,7 @@ project directories.
633641
-------------------------------------------------------------------------------
634642
The plug-in doesn't seem to work in Cygwin ~
635643

636-
If you want to use the plug-in with Vim under Cygwin [15], you need to have
644+
If you want to use the plug-in with Vim under Cygwin [20], you need to have
637645
the Cygwin version of Ctags installed instead of the Windows version (thanks
638646
to Alex Zuroff for reporting this!).
639647

@@ -644,13 +652,13 @@ Contact ~
644652
If you have questions, bug reports, suggestions, etc. the author can be
645653
contacted at peter@peterodding.com. The latest version is available at
646654
http://peterodding.com/code/vim/easytags/ and http://github.com/xolox/vim-easytags.
647-
If you like this plug-in please vote for it on Vim Online [16].
655+
If you like this plug-in please vote for it on Vim Online [21].
648656

649657
===============================================================================
650658
*easytags-license*
651659
License ~
652660

653-
This software is licensed under the MIT license [17]. Copyright 2013 Peter
661+
This software is licensed under the MIT license [22]. Copyright 2013 Peter
654662
Odding <peter@peterodding.com>.
655663

656664
===============================================================================
@@ -663,16 +671,21 @@ References ~
663671
[4] http://ftp.vim.org/vim/runtime/syntax/
664672
[5] http://ctags.sourceforge.net/languages.html
665673
[6] http://peterodding.com/code/vim/downloads/easytags.zip
666-
[7] http://peterodding.com/code/vim/shell/
667-
[8] http://en.wikipedia.org/wiki/Dynamic-link_library
668-
[9] https://npmjs.org/package/jsctags
669-
[10] http://en.wikipedia.org/wiki/Symbolic_link
670-
[11] http://en.wikipedia.org/wiki/Hard_link
671-
[12] http://en.wikipedia.org/wiki/Canonicalization
672-
[13] http://www.vim.org/scripts/script.php?script_id=1764
673-
[14] http://ctags.sourceforge.net/ctags.html#FILES
674-
[15] http://en.wikipedia.org/wiki/Cygwin
675-
[16] http://www.vim.org/scripts/script.php?script_id=3114
676-
[17] http://en.wikipedia.org/wiki/MIT_License
674+
[7] http://peterodding.com/code/vim/downloads/misc.zip
675+
[8] http://www.vim.org/scripts/script.php?script_id=2332
676+
[9] https://github.com/gmarik/vundle
677+
[10] http://github.com/xolox/vim-easytags
678+
[11] http://github.com/xolox/vim-misc
679+
[12] http://peterodding.com/code/vim/shell/
680+
[13] http://en.wikipedia.org/wiki/Dynamic-link_library
681+
[14] https://npmjs.org/package/jsctags
682+
[15] http://en.wikipedia.org/wiki/Symbolic_link
683+
[16] http://en.wikipedia.org/wiki/Hard_link
684+
[17] http://en.wikipedia.org/wiki/Canonicalization
685+
[18] http://www.vim.org/scripts/script.php?script_id=1764
686+
[19] http://ctags.sourceforge.net/ctags.html#FILES
687+
[20] http://en.wikipedia.org/wiki/Cygwin
688+
[21] http://www.vim.org/scripts/script.php?script_id=3114
689+
[22] http://en.wikipedia.org/wiki/MIT_License
677690

678691
vim: ft=help

0 commit comments

Comments
 (0)