2009/9/15 stone <[email protected]>:
> 2009/9/14 A. S. Budden <[email protected]>
>>
>> I've just added a preliminary test version (with a few bug fixes) to
>> my site
>> (http://sites.google.com/site/abudden/contents/Vim-Scripts/ctags-highlighting).
>> Please could you download this version and see whether it works (I've
>> only updated ctags_highlighting.vba)? If it doesn't, it would be
>> useful to see the debugging output that this version includes: enter
>> the following:
>>
>> :redir > ctags_hl_output.txt
>> :let g:CTagsHighlighterDebug = g:DBG_Information
>> :call UpdateTypesFile(1,0)
>> :redir END
>>
>> This will create a file called ctags_hl_output.txt in the current
>> directory with some useful debugging information. If you could post
>> this file then I should be able to work out where it's going wrong.
>>
>> Thanks,
>>
> Starting UpdateTypesFile
> Looking for ctags.exe in C:\Program Files\PC Connectivity
> Solution\,C:\WINDOWS\system32,C:\WINDOWS,C:\WINDOWS\System32\Wbem,C:\Program
> Files\Common Files\Roxio Shared\DLLShared\,C:\Program
> Files\doxygen\bin,,D:\Stone\software\install\job_tools\cvsnt,C:\Program
> Files\IVI
> Foundation\VISA\WinNT\Bin,D:\Stone\software\install\job_tools\Vim\vim72
> Not found.
[snip]
> E605: Exception not caught: Cannot find file ctags.exe
> It looks like the program can not find the ctags.exe. But I am sure the exe
> file has been in C:\WINDOWS\system32.What happened?
This is indeed very strange. The problem is coming from globpath( )
as far as I can tell: it doesn't think that the file exists. Your
path looks correct (and in the right format for globpath), so it's
bizarre that it can't find ctags.exe. Please can you try the
following?
:redir > logfile.txt
:let path = substitute($PATH, ';', ',', 'g')
:echo "Bare Path:"
:echo $PATH
:echo "Path:"
:echo path
:echo "Path Glob:"
:echo globpath(path, 'ctags.exe')
:echo "Winsys Glob:"
:echo globpath('c:\windows\system32', 'ctags.exe')
:echo "Path Glob for xcopy.exe:"
:echo globpath(path, 'xcopy.exe')
:echo "Winsys Glob for xcopy.exe:"
:echo globpath('c:\windows\system32', 'xcopy.exe')
:echo "Readable?"
:echo filereadable('c:\windows\system32\ctags.exe')
:redir END
Sorry for the tedious entry: as an alternative, save all of that to a
file (e.g. c:\testfile.vim) without the leading colons and do:
:source c:\testfile.vim
We'll get to the bottom of this in the end!
> PS:
> I have make the tag file for all symbol by use awk command. And save these
> symbols to the tag_highlight.hi file.
> Then in my _vimrc I add thiese sentences:
> if filereadable("tag_highlight.hi")
> autocmd BufRead,BufNewFile * so tag_highlight.hi
> endif
> So I can highlight my symbols in my code. But I feel some slowly when I　open
> my code file.
> How about your plugin?
> Is it using the same method?
> Will it create a tag symbol file?
> Will it make it slowly when open code file?
My plugin uses a similar method (it runs ctags, then parses it using
python to generate a symbol file). It probably adds a little delay
opening the code file, but I don't really notice it. It obviously
depends on the number of symbols and how you are doing the
highlighting. It's important that you use "syn keyword" instead of
"syn match" (as the latter is much slower) and it is beneficial to put
multiple keywords on one line (although there is a line length limit
that must be obeyed as well) in order to reduce the size of the
highlight file.
Hope that helps,
Al
--
http://sites.google.com/site/abudden
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
