Allow anchors in changeset traclinks

[anonymous]

When referencing large changesets, it would be really useful if one could enter for example [2177#file17] to link to ​http://projects.edgewall.com/trac/changeset/2177#file17

[Christian Boos]

This is a good idea, along with the general idea that the #xxx suffix should be used to refer to a particular detail in the linked object, as it's already the case for Wiki links and was recently suggested for source links (see #2011).

Alternatively, The TracDiff support the notion of restricted changeset (i.e. the changeset information restricted to what happened on a given path), which support the syntax [1234/trunk/README], since r… (wait, committing first…) since r2256.

[Christian Boos]

Depends on #2168.

There's one caveat: the generation of the #fileXYZ sequence should not depend on the diff options (currently, a file containing only white space changes will simply dissappear from the list if the ignore white-space changes option is checked)

[Christian Boos]

I think that the restricted changeset TracLinks (i.e. [1234/trunk/README]) are way better for this ticket's use case than the suggested syntax.

First, as already mentioned, the number of files shown is susceptible to change depending on the Diff options. Then, refering to a particular anchor within the full changeset is not going to help for performance when trying to view a large changeset.

[Christian Boos]

In fact, when changing the diff options, only what gets actually displayed can vary, but the #fileXYZ sequence never changes. So this might actually get implemented as part of #2168.

[Christian Boos]

Original request for enhancement implemented in r4367.

Don't forget that the first entry is #file0! But anyway, there's now an anchor which makes it easy to pick the right number without having to count ;)