-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update config roots in README #21
Comments
I don't use coc.nvim anymore, which probably explains why the documentation is out of date. I want to make sure I understand here: everything listed as being stored in I can fix the other thing, too. The way coc.nvim handled configurations really bugged me when I wrote this, so I'm glad it's more logical. |
Yes, that's it. I have not fully tested other keys (e.g. Thank you for maintaining this package even after your abandoning |
Sorry for not getting back on this sooner, but I just pushed a branch, EDIT: I just opened a PR, which is referenced below. |
Thank you for your update! I'm sorry for that I have provided the wrong information related to the config location change. Most plugins actually stored their configurations in the object root rather than in Also, during my testing, changes in |
As I work on another issue in your project, I have found that
workspace.getConfiguration('bibtex')
seems to be located atcoc.preferences.bibtex
rather thancoc.source.bibtex
as you documented in README.md. Probably your documentation should be updated to the latest changes of coc.nvim.Also, my humble suggestion: As many of the extensions store their config in
coc.preferences.*
, what do you think about movinglist.source.bibtex.*
tococ.preferences.bibtex
in accordance with other extensions?Thank you in advance.
The text was updated successfully, but these errors were encountered: