Stefan Haller 99c1bcbf23 Reset the view origin for a new task on the UI thread ... When a task renders different content to a view (a new task key), the view's scroll origin is reset to the top via onNewKey. That ran on the task's own goroutine, racing the UI thread, which reads the origin (OriginY) while laying out and drawing the view -- the single largest source of view-render data races. Give ViewBufferManager a bounce primitive (onUIThread) that runs a function on the UI thread and waits for it, and reset the origin through it. This is the first use of the primitive; subsequent commits route the rest of the task's view mutations through it too, so that the view is only ever touched on the UI thread. It runs as background work (OnUIThreadAndWaitBackground) so rendering doesn't count towards the app being busy, matching how the render's gocui task is already created. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-17 12:35:54 +02:00
..
async_handler.go	Copy gocui files into lazygit repo under pkg/gocui	2026-04-30 14:29:08 +02:00
async_handler_test.go	Copy gocui files into lazygit repo under pkg/gocui	2026-04-30 14:29:08 +02:00
tasks.go	Reset the view origin for a new task on the UI thread	2026-07-17 12:35:54 +02:00
tasks_test.go	Reset the view origin for a new task on the UI thread	2026-07-17 12:35:54 +02:00