-
Notifications
You must be signed in to change notification settings - Fork 128
View raw non-rendered markdown source with line numbers on file blob show view #297
Comments
What do you mean by this exactly? Thanks for any info! |
@aspiers ah, I (cryptically) meant "with the standard ACK reply" :-) I don't even do those updates anymore, they always reply. |
Ah right. The only workaround I found so far was to use the blame view instead, which is obviously not great. |
I'm also interested in having a repository settings option to tell github wether I want my markdown files to be rendered or wether I want to display raw markdown files (BLOB). |
I'd love this feature too! Wanted to link someone to a particular line of a longish README.md, but you either get the rendered Markdown w/o lines, or you can click "raw" and see the file w/o GitHub's nice line formatting. |
@iliastsangaris please use the new +1 button feature instead of comments to avoid notifying people and have an automated upvote count ;-) |
I got here because I was wondering how to open an issue from markdown code, so I had to figure out a workaround. Currently you have to find the .md file, press 'y' to find the blob hash, go to Blame view, find the line numbers, and then manually assemble the reference. e.g. Want to reference line 48 of
Line 48 in 001e354
|
Line 48 in 001e354
https://github.com/goswami-rahul/alien-invasion-game/blob/027071489c12df633d362351364b642443a4415f/README.md#L8 I wonder why doesn't it work in my repo? |
It works just fine. It doesn't render here, because this is |
Almost 4 years now. Any progress? |
@XedinUnknown Please note that this is a repository only for tracking gripes people have with GitHub. The operators of this repository do not have any power to add features to GitHub itself. If you are interested in seeing progress, consider using Contact GitHub to send GitHub itself feedback about the issue. See https://github.com/isaacs/github/blob/master/README.md . |
Note this question is also on StackOverflow here. As someone who works with markdown files a lot, I run into this issue all the time. I'm surprised GitHub is taking so long to address it! @cirosantilli the GitLab Feedback link in your comment now seems to redirect to a blog post.
Regarding GitLab however, there is a frontend option to "display source" (pull request). When linking to a markdown file with |
I'm rather surprised not to be able to turn off the preview for READMEs. It never mattered for me... until I wanted to link someone to a line in the readme. Wouldn't a preview button to view it rendered make sense? |
Has anyone submitted this to GitHub support as a request? I'm not sure that they check this repo. |
Any progress! I too want my markdown files to not be rendered as they are used by a jekyll project. Github renders my markdown file horribly wrong that I want it to not render it. |
Just adding my +1 ..this would be a cool feature |
Announced via https://github.blog/changelog/2021-06-30-parameter-to-disable-markdown-rendering/: Append |
Currently, it is not possible to view the highlighted markdown source with line numbers like it is possible for non-markdown files: only the rendered HTML shows:
vs
I want to do this to be able to link to specific lines of the markdown file, like can be done with other file types. Header IDs are somewhat of a workaround, but not enough as you may want to comment any specific line.
It would also enable stuff like: #295, #293 (comment) for markdown.
On GitLab: http://feedback.gitlab.com/forums/176466-general/suggestions/6563749-also-show-non-rendered-markdown-on-blob-show
This is already even possible for SVGs where you have "Display the source blob" and "Display the rendered blob" buttons: https://github.com/corkami/pics/blob/28cb0226093ed57b348723bc473cea0162dad366/binary/elf101/elf101-64.svg Come on GitHub!
The text was updated successfully, but these errors were encountered: