So if you write

#include < iostream> it will display iostream, BUT if you drop the space after "<" it simply ignore what ever you write after that.

I don't know if others are also facing this issue but I have checked it on Safari and Firefox and I am on mac.

  • 7
    Must... resist... urge... to... format... question... – mmyers Nov 18 '09 at 18:42
  • 2
    @mmyers: why fight it? – Joel Coehoorn Nov 18 '09 at 20:12
  • 2
    because Joel, it's a boy learning, and you don't want to discourage the learning – Nathan Koop Nov 18 '09 at 20:22
  • 1
    Why fight it? Because formatting it destroys the meaning of the question. – mmyers Nov 18 '09 at 20:27

#include <iostream> surround code by tick marks or

#include <iostream> // indent code by four spaces (8 after a list)

Source of the above:

`#include <iostream>` surround code by tick marks or

    #include <iostream> // indent code by four spaces (8 after a list)

There is a ? on the upper-right of the editor that explains Markdown syntax:


  • hmm, thanks man that was helpful. – itsaboutcode Nov 18 '09 at 18:47
  • +1 for answer, 6.5/10 for the drawing. – tvanfosson Nov 18 '09 at 19:00
  • Indeed, my circle-foo is weak. What's missing? – GManNickG Nov 18 '09 at 19:10
  • 2
    There aren't any faces, construction equipment, or monsters in evidence. A large spy or magnifying glass might have been appropriate. – tvanfosson Nov 18 '09 at 19:13

You need to put backticks around inline code: like <iostream> this. Or indent code blocks 4 spaces.

[space][space][space][space]Like <iostream> this

or Like `<iostream>`  this

If you just put in <iostream> it thinks you're using an HTML tag.


Alternatively, highlight the code and click on the little 101/010 icon above the text box. Or click on that icon to put in the backticks and type in the middle. That's how I did it for a long time.

You must log in to answer this question.

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