Skip to content

Commit f8dd061

Browse files
committed
version 4.2 (released on Nov 14, 2006)
1 parent f5eb37d commit f8dd061

File tree

2 files changed

+177
-61
lines changed

2 files changed

+177
-61
lines changed

doc/taglist.txt

Lines changed: 29 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Author: Yegappan Lakshmanan (yegappan AT yahoo DOT com)
44
For Vim version 6.0 and above
5-
Last change: 2006 September 6
5+
Last change: 2006 November 14
66

77
1. Overview |taglist-intro|
88
2. Taglist on the internet |taglist-internet|
@@ -63,7 +63,7 @@ programming languages. The "Tag List" plugin provides the following features:
6363

6464
The home page of the taglist plugin is at:
6565
>
66-
http://www.geocities.com/yegappan/taglist
66+
http://vim-taglist.sourceforge.net/
6767
<
6868
You can subscribe to the taglist mailing list to post your questions or
6969
suggestions for improvement or to send bug reports. Visit the following page
@@ -711,9 +711,9 @@ the PATH environment variable, then there is no need to set this variable.
711711

712712
The exuberant ctags tool can be installed under different names. When the
713713
taglist plugin starts up, if the 'Tlist_Ctags_Cmd' variable is not set, it
714-
checks for the names exuberant-ctags, ctags, ctags.exe and tags in the PATH
715-
environment variable. If any one of the named executable is found, then the
716-
Tlist_Ctags_Cmd variable is set to that name.
714+
checks for the names exuberant-ctags, exctags, ctags, ctags.exe and tags in
715+
the PATH environment variable. If any one of the named executable is found,
716+
then the Tlist_Ctags_Cmd variable is set to that name.
717717

718718
If exuberant ctags is not present in one of the directories specified in the
719719
PATH environment variable, then set this variable to point to the location of
@@ -1026,9 +1026,9 @@ The taglist plugin provides the following ex-mode commands:
10261026

10271027
*:TlistMessages*
10281028
:TlistMessages
1029-
Display the logged debug messages from the taglist plugin.
1030-
This command works only when logging to a script-local
1031-
variable.
1029+
Display the logged debug messages from the taglist plugin
1030+
in a window. This command works only when logging to a
1031+
script-local variable.
10321032

10331033
*:TlistOpen*
10341034
:TlistOpen Open and jump to the taglist window. Creates the taglist
@@ -1268,6 +1268,7 @@ A. Are you using Vim version 6.0 and above? The taglist plugin relies on the
12681268
>
12691269
:filetype
12701270
<
1271+
The output of the above command should contain "filetype detection:ON".
12711272
To turn on the filetype detection, add the following line to the .vimrc or
12721273
_vimrc file:
12731274
>
@@ -1288,19 +1289,34 @@ A. Are you using Vim version 6.0 and above? The taglist plugin relies on the
12881289
Do you have the |'shellslash'| option set? You can try disabling the
12891290
|'shellslash'| option. When the taglist plugin invokes the exuberant ctags
12901291
utility with the path to the file, if the incorrect slashes are used, then
1291-
you will see errors.
1292+
you will see errors.
1293+
1294+
Check the shell related Vim options values using the following command:
1295+
>
1296+
:set shell? shellcmdflag? shellpipe?
1297+
:set shellquote? shellredir? shellxquote?
1298+
<
1299+
If these options are set in your .vimrc or _vimrc file, try removing those
1300+
lines.
12921301

12931302
Are you using a Unix shell in a MS-Windows environment? For example,
12941303
the Unix shell from the MKS-toolkit. Do you have the SHELL environment
12951304
set to point to this shell? You can try resetting the SHELL environment
12961305
variable.
12971306

1307+
If you are using a Unix shell on MS-Windows, you should try to use
1308+
exuberant ctags that is compiled for Unix-like environments so that
1309+
exuberant ctags will understand path names with forward slash characters.
1310+
12981311
Is your filetype supported by the exuberant ctags utility? The file types
12991312
supported by the exuberant ctags utility are listed in the ctags help. If a
1300-
file type is not supported, you have to extend exuberant ctags.
1301-
1302-
Run the following command from the shell and see whether you see
1303-
your tags in the output from exuberant ctags:
1313+
file type is not supported, you have to extend exuberant ctags. You can use
1314+
the following command to list the filetypes supported by exuberant ctags:
1315+
>
1316+
ctags --list-languages
1317+
<
1318+
Run the following command from the shell prompt and check whether the tags
1319+
defined in your file are listed in the output from exuberant ctags:
13041320
>
13051321
ctags -f - --format=2 --excmd=pattern --fields=nks <filename>
13061322
<

0 commit comments

Comments
 (0)