2009/9/24 stone <[email protected]>: > > 2009/9/21 A. S. Budden <[email protected]> >>There are three possibilities that I can think of: >>1) The problem may be that you don't have the various colour groups >>defined in your colour scheme. If I'm correct, entering the following >>should help: >>:hi Type guifg=blue ctermfg=blue >>A quick test would be to enter: ":hi DefinedName" and see whether it >>reports an error. See ":help ctags_highlighting-colours" for more >>information. >> >>The above will, of course, only highlight types, but it's a good way >>of quickly testing it. If this works, the full list of highlight >>groups that need to be defined are: >> >>ClassName >>DefinedName >>Enumerator >>Function >>EnumerationName >>Member >>Structure >>Type >>Union >>GlobalConstant >>GlobalVariable >> >>A quick (but not necessarily appealing to you) way of getting all of >>these defined is to download my "Bandit" colour scheme from: >> >>http://sites.google.com/site/abudden/contents/Vim-Scripts/bandit-colour-scheme >>(save to vimfiles/colors and enter :colorscheme bandit). Of course, >>this will override your colour scheme and you may not like mine! >> >>2) A second possibility is that the generated types file isn't being >>read correctly. If this is the case, ":source types_c.vim" will fix >>the problem temporarily, but we'll need to look in a bit more detail >>to identify why it isn't being read automatically. >> >>3) The other possibility is that types_c.vim doesn't contain the >>necessary entries (check by opening it in vim). The most common >>reason for this is that the source and header files are spread over >>multiple directories and the recursive option wasn't selected. If >>your files are all in one folder, make sure you run ":cd %:p:h" before >>you run :UpdateTypesFile (to make sure you're in the correct working >>directory). If they're spread out like this: >> >>c:/path/to/ProjectDir/Source/*.c >>c:/path/to/ProjectDir/Headers/*.h >> >>or something like that, do ":cd c:/path/to/ProjectDir" then ":e >>Source/MyFile.c" followed by ":UpdateTypesFile!" (note the exclamation >>mark for recursive operation). Alternatively you do ":let >>b:TypesFileRecurse = 1" for each buffer and then you won't need the >>exclamation mark. If you use the project plugin, the CD= and in= >>parameters make all of this very easy. Hopefully I'll tidy up the >>options system in the ctags highlighting plugin very soon. >> >>Please let me know how you get on: I'm really keen to see this working for >> you! >> >>Regards, > Thank you for your reply. > I am sorry response so slowly , because I'm busy in working. > So I have try the plugin again. And I Have these results: > 1. > I am using the colortheme: "desert". So muse I use your colortheme? > When I run :hi DefinedName, the vim show: no highlight group.
You don't have to use my colour scheme, but you will have to modify the colour scheme to add the extra highlight groups. A very simple way of doing this would be to add the following lines to the end of desert.vim (it's probably better to copy it to your vimfiles/colors directory): hi link ClassName Statement hi link DefinedName Statement hi link Enumerator Statement hi link Function Statement hi link EnumerationName Statement hi link Member Statement hi link Structure Statement hi link Type Statement hi link Union Statement hi link GlobalConstant Statement hi link GlobalVariable Statement > 2. > I can not find types_c.vim in my directory.I guess the file should not been > created. > So How can I create this file. This file should have been created by :UpdateTypesFile - the fact it's not there is rather strange. How are your projects structured? Are all the files in one directory or are they in a number of subdirectories. If the latter, make sure you :cd to the bottom level directory of the project and use :UpdateTypesFile! (note the exclamation mark) to run recursively and include subdirectories. Perhaps you could run the following and let me know the output: :redir @+> :call UpdateTypesFile(1,0) :redir END (this will redirect the output into the system clipboard, so you can then paste it into an email). > 3.I have not tried yet. Please let me know how you get on with the above. 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 -~----------~----~----~----~------~----~------~--~---
