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

I noticed that on StackOverflow, a question which used the @ sign to denote a string literal ie

string TheClosingQuoteSOULDBeEscaped = @"c:\";
string ButTheSyntaxHighlightingMissesIt = "another string";

Doesn't properly handle the string literal and instead thinks the slash at the end of line one is meant to escape the last quote, leading to a mega quote that spans the whole code block. I saw this in the question listed below:

Running Command line from an ASPX page, and returning output to page


The system works!!! The ticket I opened with Google was just resolved! The project owner, mikesamuel, fixed it in under four days. Its in revision 83. As long as the SO team updates with the next release, this problem is solved.

share|improve this question
This is all Google's fault. I say we march over there and tell them off. – JSONBog Sep 29 '09 at 16:31
Oh, does SO use Google for syntax highlighting? If so, I guess that doesn't bode well for my bug getting fixed. You don't think they scan forums looking for stuff to do? – Michael La Voie Sep 29 '09 at 16:40
They will if we tell them off enough! – JSONBog Sep 29 '09 at 16:55
We're all behind you, Welbog! ...Wayyy behind you. – mmyers Sep 29 '09 at 17:08
@mmyers: Your waffly support will not go unsyrupped. – JSONBog Sep 29 '09 at 17:10
+1 for reporting the issue to Google, as indicated in your comment to Jeff. – ベレアー アダム Sep 29 '09 at 17:44
Should this be "reopened" or flagged of some sort? Typing string a = @"dir\"; string b = "hello"; does not work when I type it.. :-( Or did google do a rollback for the support of the @-sign? – Patrick Jun 15 '10 at 9:13
bug is still confirmed... – Vogel612's Shadow Jul 2 '13 at 11:50
up vote 4 down vote accepted

Yes, this has to be fixed in google-code-prettify first.

OK, we just deployed the latest trunk of prettify.js ; revision 83

share|improve this answer
I opened an issue ticket: – Michael La Voie Sep 29 '09 at 17:14
Fixed in revision 83 – Factor Mystic Oct 4 '09 at 1:59

You must log in to answer this question.

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