If it's a "paste code snippet" button that escapes the block of text, I think that'd work out okay. Better than escaping the whole thing with `~~~~` fences which would show up in a few places (like plain text notifications). And then we can add more buttons to add more formatting help too, besides just code blocks.
Other different types of solutions might be: requiring preview before post, so issues are noticed. Or having a 'view original text' button so viewers can see the original text as it was entered (this would be useful too for other cases of viewing "source markdown"). --- ** [tickets:#6822] Option to bypass or escape markdown** **Status:** open **Created:** Thu Oct 31, 2013 08:41 PM UTC by Dave Brondsema **Last Updated:** Thu Oct 31, 2013 08:43 PM UTC **Owner:** nobody All textareas take markdown input, but if you don't realize that and just type or paste something (e.g. code sample, log file) then certain chars may convert into markdown syntax and not render as actually intended. A checkbox near preview & formatting help buttons could be added. (Maybe expand to a full toolbar to help with syntax some day). Changing the data storage for every artifact and the render calls for every artifact is a lot of work and makes the whole system a bit more complex. If we can use markdown syntax to escape the whole content of the entry, that could work out pretty well I think. Requested via [forge:feature-requests:#134] and [forge:site-support:#3470] --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
