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 experience, the perceived slowness happens when
one wants to, say, unstage 2 of 100 changed files, which causes the
entire magit status buffer to be re-rendered twice. So if there
were a way to mark multiple files/chunks and then operate on them
together, that would already improve matters greatly.
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.
--
David Abrahams
BoostPro Computing
http://boostpro.com
