Allow highlight markers on browser TracLink without revision, or document limitation

[Ryan J Ollos]

The following is a valid TracLink: tags/trac-1.0/setup.py@11307:19-25#L15​

However, if the revision @11307 is omitted, we don't get a valid TracLink: tags/trac-1.0/setup.py:19-25#L15

If we add a @ without a revision number, the TracLink is valid: tags/trac-1.0/setup.py@:19-25#L15​

Documentation changes would be applied here: TracLinks#VersionControlrelatedlinks.

[Christian Boos]

Like this: TracLinks@91?

[Ryan J Ollos]

The documentation is helpful. Do you think we should also try to support highlighting with the @ omitted? I haven't looked at the code yet to determine how much effort the change will require.

[Christian Boos]

Doing without the @ separator implies using : as a separator, so source:/path/filename:1 will no longer be seen as a valid link… It won't be a problem for most people, I suppose, as : is not even a valid part of a file name on Windows (while @ is!).

But the reasoning for having a mandatory @ before specifying the range was that this way you make it clear that omitting the revision was intentional and not just an oversight (#3745).

[Ryan J Ollos]

That logic seems sound. Thank you for the documentation update.