>
>
> 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
The Vim helptags are per-directory: with the default 'runtimepath' you
could have up to five directories of helpfiles, namely (on Windows, but
in Vim termlinology) ~/vimfiles/doc, $VIM/vimfiles/doc, $VIMRUNTIME/doc,
$VIM/vimfiles/after/doc and ~/vimfiles/after/doc. The tags file in
$VIMRUNTIME/doc applies only to the helpfiles in that directory; if you
install your own additional helpfiles (which should go in the other
four) you should run :helptags in the directory in question to create or
update _its_ tagfile. (If you unpack a vimball with one or more
helpfiles in it, it will run :helptags for you, usually in
~/vimfiles/doc if you're on Windows.)
If you modify the 'runtimepath' option, you could have a tags file in
the doc/ subdirectory of each of the "tree-head" directories mentioned
(comma-separated) in your modified setting. All those will be integrated
to the Vim help, and will also be accessible by using tag commands
(:tag, :tselect, :tnext, etc., and also Normal commands such as Ctrl-]
and Ctrl-T which we learnt about the helptags, but are actually for any
tags).
If you do _not_ add the parent directory to 'runtimepath', I think (but
haven't tested) that doing :helptags on that directory would generate a
tags file from everything that is between *stars* without integrating
those tags to the Vim help. You could then use the tag commands on them,
see :help tagsrch.txt
Best regards,
Tony.
--
[SIR LAUNCELOT runs back up the stairs, grabs a rope
of the wall and swings out over the heads of the CROWD in a
swashbuckling manner towards a large window. He stops just short
of the window and is left swing pathetically back and forth.]
LAUNCELOT: Excuse me ... could somebody give me a push ...
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD
--
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
No comments:
Post a Comment