Kyle Meyer

> But @kyleam says NO! [1d9315e](https://github.com/datalad/datalad/commit/1d9315e9a30dd86bc4be0501be628f4da0a526bc) Don't listen to him, biggest wet blanket I know

> FYI I don't see `magit-debug-refresh` in the MELPA version. I think that was meant to be `magit-refresh-verbose`.

Hmm, it certainly isn't zippy on my end, but I'm not able to trigger a hang when staging region hunks (tried five stage operations in a row).

What's your version of magit-section? Perhaps you're running into this issue: https://github.com/magit/magit/issues/4695#issuecomment-1154030458

> Magit-section version is 20220615.1159. This is later than the one referenced in that issue you linked? Yes, it looks like it, so I guess that's not it (though the...

Yeah, I can't glean anything from that output either. You could try stepping through the `magit-section-goto-successor` method for hunk sections: https://github.com/magit/magit/blob/adf5848ea787401b09aa37b134aacaaaae3007f7/lisp/magit-diff.el#L2868-L2891 With the example diff above, when you stage a...

Magit depends on `compat`, and `compat` provides those functions. Perhaps this is a setup/installation issue? Do you have `compat` installed?

@johanvts (and @tarsius) sorry for not following up to the last comment in July. --- @johanvts: > I also had to switch to "%(refname:lstrip=2)" to get correct branch names. Right,...

Thanks for report. This looks like it boils down to expecting the `-c` values to be propagated to the underlying git(-annex) calls. While datalad internally uses `-c` in some of...

@dpastoor I think that's a good point (and had the similar thought when reading the initial post). And conceptually the `Tarballs` section feels more appropriate to me than `Repos` because...