Be more permissive with line number anchors

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Usability
    • None

      I've got a project that is hosted both in github and in bitbucket. This project contains documentation that links to specific lines in source files.

      In github such links have the line numbers in the fragment in the form `#L12-L15`

      In Bitbucket the fragment line numbers must be in the form `#12-15`

      On the face of it this means that the link formats are incompatible - links can either work in Bitbucket or in github but not both.

      A slight ray of hope is offered in that github will extract the line numbers from the fragment regardless of what other content is in there, so `#L12-L15,12-15` will still highlight lines 12 to 15. Perhaps it'll be possible to update our links to have both formats of line numbers?

      Unfortunately Bitbucket is stricter about the fragment contents. The same fragment will not work in Bitbucket - no lines are highlighted.

      It'd be really nice if Bitbucket were more permissive about fragment contents, making a best-effort attempt at parsing out line numbers despite the presence of unrecognised content. This would allow links that work in both environments.

              Assignee:
              Unassigned
              Reporter:
              Ryan McNally
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: