Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

help conflict : need fixing help tag; that change to plugin-prefix using #52

Open
tsuyoshicho opened this issue Jul 24, 2019 · 4 comments

Comments

@tsuyoshicho
Copy link

tsuyoshicho commented Jul 24, 2019

in help-writing

TAGS

To define a help tag, place the name between asterisks (*tag-name*).  The
tag-name should be different from all the Vim help tag names and ideally
should begin with the name of the Vim plugin.  The tag name is usually right
aligned on a line.

for example

[j in braceless.vim and vim-anyfold and helptag exception occur:

Vim(helptags):E154

rel: pseewald/vim-anyfold#27

@blueyed
Copy link

blueyed commented Jul 24, 2019

What is the conflicting tag name?

@tsuyoshicho
Copy link
Author

I see

Try it

  1. install braceless.vim and vim-anyfold.
  2. :helptag generate together.
  3. occur above error.

and then;

  1. help [j open one side (half user miss hit)

@pseewald
Copy link

I think it can not be avoided that different vim plugins define the same tags. Indeed the helptags command works on a specific directory and the documentation of each plugin is in its own doc directory so there should never be any conflict. The only way I could reproduce above error is to copy the documentation file of both plugins into the same directory and then run :helptags on that directory. With a plugin manager (vundle or pathogen), helptag generation works fine.

@tsuyoshicho
Copy link
Author

Yes, but any plugin manger some plugins gater one because keep petformance.(rtp at small keep)

I can be workaround(set split/standalone picked plugin). but it is no roor cause fix.
Suggest this issue; to under official help guideline.

If reject this, I understood policy and OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants