RMARKDOWN COLOR TEXT CODE

ID: everyone! While this appears to be something simple at first it turns out to be a rather complex undertaking with tons of implications to consider. You are receiving this because you are subscribed to this thread.Message

Reply to this email directly, view it on GitHub Generated URL as src of tag and give the needed sizes. If you want to change the original sizes of the SVG you can use the Many of the commonly used shorthand's are alreadt being implemented in contemporary markdown.Īfter making your custom text with custom colors, save the SVG file andĬlick on the *Edit* button of the *README.md*ĭrag and drop the SVG file to the opened online editor. It would take some ingenuity to implement. Where 1 equals a set of numbers ex(1-8) or (1-4) or whatever.Įach number is a different color. Wont work because most of the syntax you are suggesting is already being implemented in Markdown. Just wanted to point out that using something like I believe they are MS now, which are like the contemporary marketing gurus. Which makes since because I know that, (75% ) or more, of the time I spend in GitHub, is in my own, or someone else's, README.md documents. There MarkDown is a unique trademark of there site. It is so unique and custom, that I see editor extensions that generate markdown in the same format as GitHub does. Any of us can look at a dot MD document on GitHub, and know we are reading something in a GitHub repository.

There markdown, generates a README view that is unique onto GitHub. If I had to guess as to why they don't implement color, I would say it is because, they are the only one with black and white text & oversized headers. Its not that I think they should insert color into there markdown engine, but at the very least give a quick one liner reason as to why they won't implement color into MD rendering engine. When a company is new, they are so quick to cater to a customers needs, but when they get big like GitHub did, they can honestly care less. Many, many projects would benefit from being able to tastefully color the structured text in their documentation.ĭamn, I am surprised at how many people have been asking for color to be implemented into the GitHub markdown preview, and how long they have been asking for it w/o reply. However, there's no fallback story for tail languages and other structured text formats that aren't in your list.

RMARKDOWN COLOR TEXT CODE

Beyond the minor inconveniences of being cumbersome to create / edit / maintain, and slower for browsers to load, screenshots thwart readers from copy/pasting key snippets of text, such as the command that was executed in the screenshot - this makes the documentation less usable, and the potential work-arounds are all very ugly.Īnother use-case from issue #369: There's a reason you support auto-colorization of code blocks - coloring text is crucial for facilitating our eyes to parse it faster. Screenshots are inferior to natively colored text. Please fix this and sunset one of my most popular StackOverflow questions (another +358 upvotes and counting): Ĭolor is an important design feature for many CLI tools, including my underscore-cli tool for hacking on JSON data, and thus, it's important to be able to include properly colored output examples in the documentation.Ĭurrently, the ONLY way to accomplish this is with a screenshot:

(I'm exaggerating only slightly the real number is 76 posts)

+1000, which is a roughly accurate summation of six years worth of continuous +1 posts on issue #369, most of which weren't noticed due to that issue being closed for most of that time.

Rmarkdown color text