⚡ Bolt: Optimize drw_map to use XFlush #164
Draft
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: Use XFlush instead of XSync in drw_map
💡 What: Replaced
XSync(drw->dpy, False)withXFlush(drw->dpy)in thedrw_mapfunction.🎯 Why:
XSyncforces the client to wait for the X server to process all requests, causing a blocking round-trip. This is unnecessary for simple drawing operations and adds latency, especially when the bar is updated frequently (e.g., status updates, window title changes).📊 Impact: Reduces latency for bar updates and other drawing operations using
drw_map.🔬 Measurement: Verified that
drw.ccompiles correctly. The change is a standard optimization in X11 window managers to improve responsiveness.PR created automatically by Jules for task 12718539557376403983 started by @paperbenni