Skip to main content
12 events
when toggle format what by license comment
Sep 9, 2015 at 12:22 comment added Spikatrix @PaulDraper Do you mean "If the author uses a ☂, show a ☂,"
Sep 9, 2015 at 7:58 comment added Paul Draper You can't tell. So don't substitute characters. If the author uses a hyphen, show a hyphen. If the author uses an em dash, show an em dash. If the author uses a ☂, show a ☂.
Dec 7, 2013 at 20:30 comment added TheMaskedCucumber How do we tell the difference ? By thinking. With a human brain.
Aug 16, 2013 at 15:57 comment added Eric You force the user to type How do I "accept" an answer -- where do I click?, with an extra space, as suggested here
Nov 22, 2012 at 7:03 comment added Kirk Woll @Camilo, indeed, if it's processor intensive, then do it in Javascript like SO already does in the preview window. "Performance" is a canard.
Jan 7, 2012 at 23:18 comment added Camilo Martin Markdown in titles too processor-intensive? We just need a backtick in the titles to delimit code - it's trivial to implement! And I'm sure it's not processor intensive, it can't be.
Feb 16, 2011 at 17:19 comment added John Bachir What is $...$?
Feb 7, 2011 at 18:31 comment added jcolebrand Or give us another delimiter to use in titles besides backtick?
Oct 29, 2010 at 7:23 comment added Konrad Rudolph trivial: there is no difference. Let the users be explicit: only filter out backtick-delimited sections. This should be straightforward (and is already done for $…$ on other SE sites).
Oct 28, 2010 at 22:25 comment added Jon Seigel Neither of those titles contain code -- auto-code-interpretation is way too much. Allow it within backquotes and that's it.
Oct 28, 2010 at 21:29 comment added jjnguy So you are going to leave the functionality that converts -- to ?
Oct 28, 2010 at 21:27 history answered Jeff Atwood CC BY-SA 2.5