rst support
See original GitHub issueIs there a way to test locally how .rst
(restructured text) would look like on github?
Issue Analytics
- State:
- Created 8 years ago
- Reactions:13
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Support for Intel® Rapid Storage Technology (Intel® RST)
Find support information for Intel® Rapid Storage Technology (Intel® RST), which may include featured content, downloads, specifications, or warranty.
Read more >Intel RST - Official Ubuntu Documentation
Overview. Intel Rapid Storage Technology (RST) is a solution built into a range of Intel chipsets. On platforms that have RST support built...
Read more >RST Support
Support Portal (RST). Welcome. Login Sign up · Home Solutions. How can we help you today? Enter your ...
Read more >Contact Us & Customer Service | RST Brands
To receive a refund, you must contact RST by calling (877)924-2090, or email returns@rstbrands.com. You may return new items purchased directly from rstbrands....
Read more >reStructuredText support | PyCharm Documentation - JetBrains
You can open any existing file with the restructured text or create a new one from scratch. Create an .rst file. Right-click in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I still don’t have a strong intention to include this since GitHub’s Readme API doesn’t support it. But since this keeps coming up (#92, #37, #113), and with the newfound focus on the offline renderer (#35), it might be worth taking a serious look.
Keeping this open for discussion and implementation advice.
https://github.com/github/markup is described as “The code we use to render README.your_favorite_markup” so I would guess that the list of supported formats there (which includes
.rst
) matters more to users ofgrip
than the list of supported formats for the API thatgrip
calls ( https://developer.github.com/v3/markdown/ ). To end users ofgrip
, the calling of that API probably feels like an implementation detail of howgrip
works internally.https://github.com/github/markup/blob/master/lib/github/commands/rest2html appears to be the Python script GitHub uses to turn
.rst
files into HTML. I kind of feel like that whole library could/should be wrapped bygrip
or something similar. That way you’d get all the formats.