> > I suspect a misconfiguration somewhere in my system.
> > How to get links with dashes working?
>
> Do hyperlinks *without* dashes work in the same file? I got the same
> errors before I did the following two things:
Yes, they work.
> 1. Put the help file in a subdirectory of your
> 'runtimepath' appended with 'doc'
>
> So, if :se rtp? returns:
>
> runtimepath=~/.vim,/usr/share/vim/vim73,~/.vim/after
It does.
> In order to be found as a *help* tag, the file would
> need to be in one of these directories:
>
> ~/.vim/doc
There it is.
> 2. Build the help tags index for that file using the
> :helpt[ags] command.
>
> If your file is in ~/.vim/doc, call it as:
>
> :helpt ~/.vim/doc
Done.
> Doing both of those things seemed to fix the problem for
> this sample file:
>
> ==> ~/.vim/doc/helptest.txt <==
> Dest for *asdf-fdsa*
> Link to |asdf-fdsa|
E426: tag not found: asdf
>
> Dest for *abcd*
> Link to |abcd|
Works
>
> Dest for *efgh*
> Link to |efgh-XXXXXXXX|
> Link to |XXXXXXXX-efgh|
Jumps to *efgh* if cursor is located on the efgh part,
error otherwise.
>
> The last two links show that Vim will fall back to splitting on hyphens
> if the whole isn't found. Only works for the efgh portion of the
> link... I guess the thought is that a plugin might forget to update a
> link: e.g. |mypluginname-oldoption| still finds:
> *mypluginname* even if there's no destination for the entire tag.
> ===============================
>
> :e ~/.vim/doc/helptest.txt
> :se ft=help bt=help
^^^^^^^
Ahhh! The buftype was missing. Thank you. This solved the
problem. I didn't know that a buftype exists, I always
worked with filetype.
Thanks.
Marco
--
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