Re: documenting my own plugins?

> Indeed, this worked:
>
> :set runtimepath=~/.vim/ftplugin/foo,$VIMRUNTIME
>
> I assume I can add it to .vimrc, so I don't need to do it every time.

Although this works, the "normal" way is to put your foo.txt help file
in ~/.vim/doc.

An alternative is to use packages, see ":help package-create". This has
the advantage that related files for the "foo" plugin are under one
directory. That matters if you want to move the plugin.

--
hundred-and-one symptoms of being an internet addict:
156. You forget your friend's name but not her e-mail address.

/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20230612201811.527FE1C0758%40moolenaar.net.