Timeline for Backslash escaping in code regions in comments
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2011 at 7:02 | vote | accept | Tomalak | ||
| Feb 14, 2011 at 21:09 | comment | added | Hendrik Vogt | Yes, I've seen that it's "status-planned". Great! Have you seen my recent bug report about wrong rendering of old comments due to the recent change of backslash escaping? Hope it's OK pointing you there via this comment. | |
| Feb 14, 2011 at 21:05 | comment | added | Jeff Atwood StaffMod | @hendrik there is still, as you noted, the issue with code blocks which end in backslash. We will also support the double-backtick method for this, and @balpha will check that in this week sometime. See: meta.stackoverflow.com/questions/78499/… | |
| Feb 14, 2011 at 11:15 | comment | added | Hendrik Vogt | Wow, that's good. Now I'll have to try and make the tex.sx users aware of this, and rewrite my explanations about inline code in comments. | |
| Feb 14, 2011 at 8:31 | comment | added | Tomalak | Thanks, that's great news! One question remains - how are the existing comments handled? | |
| Feb 14, 2011 at 2:06 | history | answered | Jeff AtwoodStaffMod | CC BY-SA 2.5 |