Repository navigation
fix(agenda): yield while preparing agenda entries - #1200
Open
dtvillafana wants to merge 1 commit into
Open
dtvillafana wants to merge 1 commit into
dtvillafana wants to merge 1 commit into
Conversation
AI-assisted: OpenCode
dtvillafana
force-pushed
the
uncapture-main-thread
branch
from
October 15, 2026 18:43
9b2086c to
009e965
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Keep daily/weekly agenda preparation responsive when scanning many large Org files. All configured files and eligible headlines are processed to completion; the work budget controls when to yield, not which entries are included.
This follows the existing notification scanner’s
Promise.async,Promise.yield, andOrgFile:parse_asyncpatterns. It is cooperative scheduling, not background-thread processing. Buffer-backed parsing, the parser timeout fallback, and final rendering can still run synchronously.Related Issues
None linked.
Changes
The branch contains a single agenda-responsiveness commit on upstream
master, without earlier fork-specific changes. No configuration options or user-facing commands change, so no user documentation update is needed.Checklist
I confirm that I have:
stylua --check lua/ tests/andgit diff --checkpass.make test.AI-assisted: OpenCode, GPT-6.1-sol