What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 127 Stack Exchange communities.

Since Stack Exchange already supports <kbd> for text input, it only makes sense to support the matching output from a program, <samp>, distinctly from the program <code> itself.

If there is value to supporting <pre> and these others in addition to Markdown's backticks and indent, adding <samp> would provide similar value, both in allowing HTML to be pasted and supported, as well as styling context (such as not attempting to syntax highlight the content).

share|improve this question

This question has an open bounty worth +50 reputation from Arkanon ending in 5 days.

This question has not received enough attention.

I strongly agree that the <samp> tag should be supported in Stack Overflow markup. Despite this question making the case well, more than four years have passed without support being added for the <samp> tag, and I'm hoping that drawing attention to this request will change that.

3  
Also, please add support for <blink> and <marquee> tags. ;) –  Alconja Mar 18 '10 at 22:25
2  
Those are presentational, rather than semantic markup! –  brianary Mar 19 '10 at 14:19
    
What do you mean by "support"? What would text in such a tag look like? –  Ether Mar 20 '10 at 2:47
2  
By "support" I mean adding it to the list of allowed tags; not stripping it. As far as style, I'd assume it would look similar to <kbd>, i.e. monospace font, maybe different colors or bolded. –  brianary Mar 22 '10 at 5:23
    
Hey, you're not Bryan Helmkamp! (brynary.com) –  macek Apr 16 '10 at 14:47
    
1  
I was just about to ask this same question, then found to my disappointment that it was asked more than four years ago and still the samp element is not supported in Stack Overflow markup. –  Arkanon Jul 6 at 10:08
add comment

1 Answer

What benefit would this give over using backticks (sparingly), the existing 4 spaces for code, or the existing <code> and <pre> tags?

For example:

<code>
This is the output from using the `<code>` tag.
You get new lines where you want them.
</code>

This is the output from using the <code> tag. You get new lines where you want them.

<pre>
This is the output from using the `pre` tag.
The text is smaller and you can't show text inside angled brackets - like `<this>`.
</pre>
This is the output from using the `pre` tag.
The text is smaller and you can't show text inside angled brackets - like ``.

If you use <!-- language: lang-none --> before the output then it won't be given any syntax highlighting.

share|improve this answer
    
Because <samp> has more characters than <pre>, and makes you feel like you're doing something with your life than just doing the bare minimum –  random yesterday
3  
What benefit does <code> or <pre> have over indenting? To start, pasting HTML content without having to manually convert it to Markdown. It also provides more specific context for styling (so syntax highlighting could be disabled, for example). –  brianary yesterday
    
@brianary - you should make that case in the question. At the moment it's just a bald statement - "SE should do X" without giving any benefits to the users of the sites. –  ChrisF yesterday
    
@ChrisF Fair enough. Added. –  brianary yesterday
add comment

You must log in to answer this question.

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