-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Howto display source code of markdown files? #13640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
usually in the upper area there are shown links "Raw Permalink Blame History" just use |
Unfortunately, no. For example, on https://gitea.com/gitea/tea/src/branch/master/CHANGELOG.md you see the rendered md-file which is nice. But when you click on the first raw-button you get nearly the same rendered result and not the source code of the md-file. The only work-around for the source code is the blame-button but it could be hard to read. |
Oh, you are right - when I deactivated the markdown add-on I get the same raw output as you. Many thanks for that advice! Nonetheless, I would like to propose an extra source-code-button next to the raw-button which displays the file with line numbers and syntax highlighting. Is there an existing configuration option for that or is it a new feature request? |
For those files who can be rendered, it will be rendered when you visit the file. For other text files, it will be a highlight code review. So I think it's may useful sometimes to view a hightlight code of the markdown file. @jolheiser I think this should be a proposal but not a question. I will change that. |
Essentiall this needs a rendered/source view, similar to SVG files which also suffer from this issue. |
When I browse through the file tree of my repo I find some markdown files (*.md). And when I click on it they are rendered (bold head lines, nice bullet lists, and so on...) which is nice for the most cases.
But in my case I just want to see the plain source code of the *.md file. How can I switch?
The text was updated successfully, but these errors were encountered: