This would make Literate CoffeeScript interoperate with existing markdown tools very smoothly.
@databases: markdown is a superset of litcoffee. Litcoffee requires code blocks to be valid coffeescript. Your proposed extension would not be able to support proper highlighting.
I don't understand your comment. I understand that there are Markdown files that are not valid .litcoffee files. But what I'm saying is that if I write something like coffee foo.coffee.md, I want the CoffeeScript interpreter to run it as if it was a valid .litcoffee file. Right now, it assumes that foo.coffee.md is a coffeescript file and borks.
I don't see anything about this proposal that would interfere with proper highlighting, but I am obviously missing something.
Ah, okay. That is reasonable. I misunderstood your proposal.
.coffee.md sounds like a fine one to add.