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

Writing a question including a C code in a <pre><code> block, I found out that in my #include lines the header names are not displayed when using the standard <name.h> convention. Instead, I had to use quotes "name.h" to make it appear. Apparently, the renderer treats these as tags, and I could not find a way to escape them. So, what is the method for doing it?

share|improve this question
    
You don't have to wrap them in <pre><code> blocks yourself. Just use standard markdown formatting. Doing this should have your includes appear just fine. –  Bart Oct 12 '12 at 0:44
    
Bart - if by "standard" you mean four spaces, please see my reply to @blahdiblah. –  ysap Oct 12 '12 at 0:50
2  
Yep, 4 space indentation. Ctrl-k. Simple as that. –  Bart Oct 12 '12 at 0:55

1 Answer 1

up vote 11 down vote accepted

The standard way of including code is by indenting it all with four spaces:

like so

(literal text: "    like so")

Or, for inline blocks, surrounding it with backticks like so (literal text: "`like so`").

As you've seen, using <pre><code> has unexpected limitations and also doesn't support nifty stuff like automatic code coloring.

That said, if you really want < and > you can get them with &lt; and &gt;

<foo>
share|improve this answer
1  
Sure, this is easy for short code pieces, but when you have a long block, it is tiring to add and/or remove all these spaces while still maintaining the original indentation/tabulation. –  ysap Oct 12 '12 at 0:48
6  
@ysap, select the code and hit Ctrl + K or use the code indent button on the formatting toolbar, looks like {}. I suggest hitting the question mark button on the right side of the formatting toolbar for additional editing help. –  Charles Oct 12 '12 at 0:50
    
blahdiblah - thanks for the update. This is what I was looking for. –  ysap Oct 12 '12 at 0:52
    
@Charles - thanks. This is definitely the best way to do this. However, my past experience is that I went into troubles using this operation - probably my fault, but once I learned about that <pre><code> feature, I decided that this must be the best way, as the code does not need any change to be displayed as code... apparently, the #include directive proved that even this has its own limitations. –  ysap Oct 12 '12 at 0:55

You must log in to answer this question.

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