Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 155 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

Possible Duplicate:
Syntax highlighting misinterprets shell code as C

In this answer, everythng after the '/*' shows as a comment (but this isn't happening in the preview). Is this a bug? If not, how can I tell Markdown that this is part of the code? I tried backticks instead of indenting, but then the indenting I had in the code was stripped out.

share|improve this question

marked as duplicate by YOU, Jeff Atwood Apr 9 '11 at 3:42

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

2  
make sure the question contains a tag that hints the code is shell code – Jeff Atwood Apr 9 '11 at 3:43
up vote 3 down vote accepted

I have edited for you, like this

<!-- language: bash -->

    FILES=pathto/*
    for f in $FILES ; do
        echo "#extra text" >> $f
    done
share|improve this answer
    
Thanks for the infor and edit! – GreenMatt Apr 8 '11 at 16:08
1  
@green in this case there were two strong "language" tags fighting which caused the syntax highlighting to revert to default. I removed the shell tag. – Jeff Atwood Apr 9 '11 at 3:44

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