Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

With type questions it would be nice if stack had a way highlight the matched parts, for instance if some like:

$ grep --color '[a-z]' <<< '123abc45ef'

It would be nice to have a way to render the matched part say red:

$ grep --color '[a-z]' <<< '123abc45ef'
share|improve this question
Sorry but your request makes very little sense. Example might help. – Shadow Wizard Jan 3 '13 at 8:42
He's talking about extending markdown to basically allow you to change the color of text inside of a code / block quote block, so that matches could be highlighted for easier reading. The request isn't off base, I just don't see a use case where simply indicating what matched or didn't match wouldn't work. – Tim Post Jan 3 '13 at 8:51
@TimPost see my answer here, the second grep is slightly confusing as it highlights blue He and Wo. – iiSeymour Jan 3 '13 at 8:59
@sudo_O Ahhh, so what you want is just more granular control of the syntax highlighting? – Tim Post Jan 3 '13 at 9:03
@TimPost yes, I think it would be helpful. – iiSeymour Jan 3 '13 at 9:05
@TimPost: I sense fun there...I'm sure there will be users which completely fail to tag their questions properly and then use that markdown to simulate syntax highlighting. – Time Traveling Bobby Jan 3 '13 at 9:13

A request for allowing users to customise font colours has been requested before and declined. IMHO, rightly so. Considering how some users abuse bold and code markup to highlight portions of text which they think is important, the thought of adding font colours to their bag of tricks makes me cringe.

As for customising the colours used in syntax highlighting, I believe Google Code Prettify is used so any related feature requests would have to be posted upstream. However, do note that highlighting is performed based on syntax, not markup, so the sample usage as you've posted in the question is unlikely to be adopted.

In the case of your answer where the default highlighting is potentially misleading, a possible compromise would be to disable syntax highlighting (it would however make your grep --color example moot). Simply use <pre> instead of indenting the code block, or precede the code block with <!-- language: lang-none --> (see syntax highlight language hints).

If specific text colour is absolutely essential to the post, use a small screenshot.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .