-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Message on startup #40
Comments
Its touched on here: https://who.ldelossa.is/posts/gh-nvim/#cli-dependencies The background refresh keeps gh.nvim in sync with the GitHub api. But it wont do much if a pr is not open, or issue buffers arent open. Its required to get new comments / new PR commits / etc... automatically. |
Ok, thanks! Still, I think the echo on neovim startup is unnecessary. Would you mind to make it optional? |
Sounds find to me. Want to send a PR for this? Ill approve. |
I'm looking into it. I'm wondering: do we really need to start the refresh timer within Line 265 in caed363
I mean, it is understandable that we want this timer when we open a PR or issue, but do we want it already when a user does the My intuition would be that we could just remove that line. It would resolve my issue. But perhaps I'm missing something? |
The timer is used to refresh arbitrary Issue buffers which can be open at any time, and unrelated to having an open PR. Its a lot simpler to just launch the timer which runs a no-op function if no Issues or PR is open, rather then trying to ref count open Issue buffers or open PRs. The no-op timer is not going to effect UX or performance when no Issue or PR buffers are open. |
Closing this as we can continue the discussion in #42. |
Hi. I like your project and believe I will be using it. However, after a relatively recent update, gh.nvim will echo "[gh.nvim] started background refresh with interval 3 minutes" when I start neovim. It does not seem useful and at the very least, it seems out of place in this context. I suggest either of the following actions:
Also: The background refresh is not explained in the docs and it is unclear what it is.
The text was updated successfully, but these errors were encountered: