2009/9/25 stone <[email protected]>: [snip] >> Please let me know how you get on with the above. > Thank for your reply. > I am so happy that the plugin have worked OK!
Excellent, I'm really pleased! > It is a very good plugin. The tags file it created run faster than my tags > file. > I add the "hi link" and run the command UpdateTypeFile!. So it can work. It > is my mistake do not prepare the color scheme. [snip] > One question. When I add or modify my define such as MACRO. Should I need > run the UpdateTypeFile! again? Yes, it only works if you tell it to update the files. > Do you have good way to run the command auto or timely? At the moment, no. I tend to find that I only occasionally add new macros etc, so I tend to run it manually (it is quite slow) after each significant change. It would be fairly easy to integrate into the make process if you're using make and wanted to do that. Basically run: c:\path\to\vimfiles\extra_source\mktypes\dist\mktypes.exe --ctags-dir="C:\WINDOWS\system32" -r from the project root directory as part of the make process. Then you just need something in vim to run :ReadTypes on any open files. > And do your plugin used cscope? Yes and no. It doesn't use cscope at all, but (for my purposes), I have configured it to run cscope in the background to regenerate the cscope.out database (so I can update the tags, types and cscope database in one go). It only does this if both of the following conditions are true: 1) There is a file in the current directory called cscope.files 2) The buffer-local variable b:CheckForCScopeFiles is set to 1. All the best, 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 -~----------~----~----~----~------~----~------~--~---
