Please document the URL fragment format for referencing line and column ranges such as L1C2-L1C4

[babenek]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

Hello.
It appears that GitHub supports URL fragments for linking to specific lines in code (e.g., #L1-L2).
However, there is no official documentation for linking to specific columns within lines (e.g., #L2C4-L2C16).

Could you please clarify whether this format is supported, and if so, document its usage for both lines and columns in code files (even it is experimental)?

Unfortunately even GitHub copilot does not know the feature but has kindly provided the way to create the issue :)

Thank you.

What part(s) of the article would you like to see updated?

content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet

• there are no info about column selection support

Additional information

Example: https://github.com/github/docs/blob/main/README.md?plain=1#L2C4-L2C16

This is the best way to pinpoint a problem spot, especially in a very long line.

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Sharra-writes]

@babenek Thanks for opening an issue! Since we don't have an answer for this, could you start with our support team? They're better equipped to hunt down the answers to whether a feature exists than the docs team. After you get an answer, though, we would love to discuss documenting it with you!

I'm going to close this issue for now, but you can comment on it and ping me to get it reopened when you have an answer, or open a new one. Either way is fine!

[babenek]

@Sharra-writes
https://github.com/orgs/community/discussions/176541#discussioncomment-14652831
I have a doubt that the discussion may help to create the documentation link for the "experemental" feature :(
Or i was wrong to create the discussion with wrong labels?

[Sharra-writes]

@babenek You're fine! The way your phrased your question in the issue just made it sound like you didn't have an answer. I'll happily reopen this and ask about how/whether we want to document experimental features!

[Deliba648]

Yeni olduğum için tam çözmüş değilim fakat emeği geçen herkese teşekkür ederim

[Sharra-writes]

@babenek Our docs aren't and can't be comprehensive if only because we would never be able to keep up with updating them with such a small team. After some discussion with the team, this is too much of an edge case for us to document, especially since it isn't officially supported currently and we tend to avoid documenting features that aren't actually supported. Sorry we can't help you with this one.