Tony Mechelynck-2 wrote: > > > Another thing not yet discussed here is that you should NEVER > modify-in-place any file in the $VIMRUNTIME directory or below it at any > depth. The reason is that any runtime file upgrade may (and sooner or > later some update is bound to) remove your modifications without any > warning -- unless you let your runtime files go stale, which is of > course not recommended. > > aleCodd, I don't know why you want to set the filetype of Vim's > helpfiles diff.txt (which is about viewing file differences in Vim > -usually in vimdiff-) and vi_diff.txt (which is about usage differences > between Vim and vi) to something other than help. IMHO this desire of > yours is misguided, but if you still want to carry on with it by > modifying the helpfiles, you should first copy them to ~/.vim/doc/ (on > Unix) or ~/vimfiles/doc/ (on Windows) and apply any modifications to the > copies. > > > Best regards, > Tony. >
Thanks for your reply, and just to clarify, 'diff' what just an example and actually what i want to do is to write syntax scripts for help files i build myself from the various documentations like php etc. now what i would like to do is to build a separate directory with php help files and run the helptags command on that directory, but that will destroy the vim help tags, so is there a way to build help-style tags (i.e. string between asterisks) and allocate a command equivalent to :help so i would be able to search the php documentation from the command line according to tags, but still be left with the original :help command for vim help files. thanks so much alex -- View this message in context: http://old.nabble.com/set-filetype-in-.vimrc-tp28931594p28944900.html Sent from the Vim - General mailing list archive at Nabble.com. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
