This repository has been archived by the owner on May 16, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Keywordprg returns not-found #79
Comments
If you've tried using it in actual code then it's not yet implemented, see #61. |
Thank you for answer @luckasRanarison I saw the issue #61 but I though the limitation is that LSPHover is overriding it. With different keymap this doesn't seem to be a problem. But I guess issue is somewhere else as well. I am closing the issue. |
The tricky part of that is the re-implementation of the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have tried using
DevdocsKeywordprg
module and have set in my options viavim.opt.keywordprg=":DevdocsKeywordprg"
. It correctly calls it but it never finds documentation even though I have tested on function such asuseState
, which entry definitely exists in React docs. Can be verified by opening Devdocs and searching for it. Calling it as a command i.e.DevdocsKeywordprg useState
does not return results either.Furthermore, I am sure LSP is not overwriting it because I get notified by devdocs and my mapping for calling it is:
Steps to reproduce:
ERROR [nvim-devdocs] No documentation found for <textobject>
The text was updated successfully, but these errors were encountered: