⚡ Bolt: Remove synchronous X call in drawing path #183
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.
⚡ Bolt: Remove synchronous X call in drawing path
💡 What: Removed
XSync(drw->dpy, False);fromdrw_mapindrw.c.🎯 Why:
XSyncforces the client to wait for the X server to process the request, creating significant latency (network round-trip + context switch) for every drawing operation. This is a bottleneck for UI updates like the status bar.📊 Impact: Reduces latency for all drawing operations using
drw_map. In high-frequency update scenarios (e.g., animations, typing), this prevents the window manager from blocking on the X server.🔬 Measurement: Verified that the project builds correctly with
make clean && make. Visual verification (via code review) confirms that event loop processing will implicitly handle flushing, makingXSyncredundant.PR created automatically by Jules for task 7670473945907552637 started by @paperbenni