Gerhard Olsson

> > That would be priority OrderBy so the expression ^(origin|upstream)$ could be written as ^(origin)$;^(upstream)$ so it can be split in two. Will users understand that? > > Yes,...

Format is as specified by Garmin (same as from Garmin Connect too what I see), but Strava does seem to interpret this differently, at least in exports. GPX could be...

Short answer: No GE parses git-diff output to determine filenames, what lines that are changed and to apply coloring, so difftastic filter will cause this parsing to fail. However, #11590...

I have played around a little with this. It is not obvious how to do this, but first some examples All of these requires #11628 (that has other dependencies), most...

A draft with integration of file numbers is in tmp/git-coloring Tests are needed An example with the combined side-by-side and single line presentation used:   Difftastic is not designed...

> Can we not convert this task into something like - configure custom merge and diff tool? Because i would like to use the difftool of intellj for example like...

An update pushed to tmp/git-coloring. There are some parsing issues, Difftastic is not intended to be used this way. But the output is quite useful. A PR will depend on...

There has been improvements to the straightening of segments, maybe this is related. Adding printouts in RevisionGraph:BuildOrderedRowCache(), every call requires seconds. CreateOrReuseLane() uses 42% or so cpu. @mstv any hints?...

The loading is much better with #11268, that handles scores for parents already in the grid. Time is maybe 15s, still slower than in 4.1 (I had not planned to...

This is improved in #11294 but loading is still slower. (and not so much improvement in #11268, almost all time is spent in StraightenLanes())