David Abrahams <[email protected]> writes: > On Apr 23, 2009, at 4:20 AM, Steve Purcell wrote: > >> >> On 23 Apr 2009, at 00:48, Marius Vollmer wrote: >> >>> >>> Yes. I suspect there is still some quadratic algorithm hidden >>> somewhere. >>> >> >> I agree that Magit's slow to work with when the changesets get big, >> but I'm not sure the key problem is the latency of rendering the >> status buffer, and the simplicity of the current model has its >> advantages. [...] > > In my case, I moved a directory and then had some individual staging > choices to make. Eventually I discovered I was better off staging > everything and unstaging the changes I didn't want. Even then, I'd > get like 10-15 second delays after each operation.
Yeah, I am pretty convinced that setting up the status buffer is the slow part, and that it doesn't need to be so slow at all. I prefer making it fast to adding features that will regenerate it less often like marking multiple files that are then staged/unstaged together. The latter just doesn't fit Magit's UI 'paradigm'. I think all that is needed to delay washing the diffs until a section is first shown. That is not entirely trivial, but would be a huge improvement. Let's see...
