One of the things that we often get feedback on is our markup. It's a custom, hacked on subset of markdown which has had, shall we say, issues. Today we made some important changes to how we deal with our markdown so we can do things like bold and italicize things willy nilly and deal with links with parentheses without bleeding all over the place.
Exciting, I know.
Basically, you should be able to properly nest markup as well as escape symbols such as * with a backlash (\). The changes we made should also allow us to more easily add more formatting options.
Big thanks to kleinbl00 for taking time to test out the new code. If you want to know some of the more technical aspects behind the changes I made a post here. As always, feedback is welcome.
I have a line break
And it was right there
Do I still need to put two spaces first
edit: By the way, this was a long time coming and I know you put a lot of work in to it. Thank you for that. like this?
You need to have two returns in order for it to turn into a line break. This probably isn't optimal, and is a quirk I've seen elsewhere that I've probably just gotten used to. I'll see about making a more sensible line break policy.
I know that a lot of the writers (ahem... lil) would appreciate that.
Test
Test Any chance we could get something that doesn't automatically remove extraneous line spaces between text? Like above, I hit enter a couple times but the words are still directly next to each other. "Email" formatting is really useful for long posts, poetry, etc. EDIT: this is similar to what thenewgreen was saying ... more flexibility with line breaks in general would be awesome. I really, really, really appreciate the markup changes -- it's something seemingly small that can drastically affect site usability. EDIT2: we still don't have strikethrough, if that's a basic add that you haven't made because there wasn't any demand, know that there's at least a bit of demand. Also, and more importantly, I still can't see the 'markup' button when I'm replying to a post rather than a comment. That's a bigger deal.
Ooohhhh, I think I see now, it's not showing up on the pub id page such as this one.
Oh geez. I think I've found the bug for why it doesn't show up for me. Hopefully when I fix it it will also fix it for you : /
Okay, I think I fixed it, tell me what you see.
Nope. Let me know if you want screenshots. Basically, I have the markup button when I'm replying to comments, or to notifications, but not when I reply to the main post. Absolutely no idea why. EDIT: also when I'm on notifications page and I hit 'parent', the reply box that pops up is missing the markup button. (This is separate from the box that appears when I just hit 'reply' -- that one's fine.)
Ya, if you could screenshot it that'd be awesome. At this point I'm looking for a mess-with-flagamuffin function hidden somewhere in the code.
I'm in firefox with the dark theme and I can see it too.I assume this is the link you are referring to?
Oh. Doh. Ignore my original comment. Yeah I see that. The link is broken into two links because it has to style each section separately with spans: Easiest fix would be to turn off text-decoration: underline for a:hover. Or figure out a way to place the a tags outside the initial span so it styles the entire <a&62;<span&62; <span&62;</span&62;<span&62;</span&62; </span&62;</a&62; rather than each individual child span.
Should be fixed now. Test: <a><span><span></span><span></span></span></span></a>
Looks fine here but was still broken the same as before the email notoficatipn. I don't think that matters though. Just FYI
forwardslash - i broke it! what I typed to create error: 
Oh geez, I think I know what's wrong here. We're a little too aggressive in escaping characters it seems. Also we didn't take into account the escaped characters have #'s in them so it things that there are tag links.
Well at least you know what the problem is. :)