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

Add support for updating forge notifications when the counter changes #680

Merged
merged 2 commits into from
Dec 1, 2023

Conversation

benthamite
Copy link
Contributor

@benthamite benthamite commented Nov 29, 2023

I’m not sure if there is interest in this functionality, but I thought it could be useful for those who use forge to check GitHub notifications. It modifies doom-modeline--github-fetch-notifications and adds a user option, doom-modeline-github-update-forge, such that when its value is non-nil, an update to doom-modeline--github-notification-number will trigger the fetching of notifications in forge. This ensures that the notification counter correctly reflects the number of forge unread notifications, which may otherwise diverge.

I’m relatively new to programming and Elisp specifically, so feel free to reject or suggest revisions.

@seagle0128
Copy link
Owner

I think it's better add a hook, and let the users make the decision.

@benthamite
Copy link
Contributor Author

Makes sense. Let me know if this works.

@seagle0128 seagle0128 merged commit ca9637e into seagle0128:master Dec 1, 2023
6 checks passed
qingshuizheng pushed a commit to qingshuizheng/doom-modeline that referenced this pull request Dec 5, 2023
…seagle0128#680)

* Add support for updating forge notifications when the counter changes

* Switch to hook-based approach
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

Successfully merging this pull request may close these issues.

2 participants