I have users who edit their quote syntax poorly and cause the quote function to fail. For example we have this one from a current topic. This is un-escaped: [quote=“CFO.Digest.Input, post:1, topic:3258”] he suggested that I put mineral oil back in. [/quote] The problem is that the /quote is in st…

This was a conscious change a few years ago: [图片] Discourse CommonMark migration plans confetti_ball balloon dev I may pull this out to another topic, but I feel that I need to hammer_and_wrench hamster some stuff. Inline multiline quote[quote]that spans lines and block…

Oh my… so we’re basically enforcing coding standards on our customers and users? While I agree with Sam’s analysis of the format, there is a difference between being difficult for the writer to read and difficult for everyone viewing the post to read. Kinda seems like we’re punishing the readers fo…

[图片] Cardinalflyer: Edit: Another option would be to force a line feed after the [/quote] if there isn’t one there… auto-edit the format for readability. That doesn’t seem like a bad idea, but if they just select text and use the quote button it works. They are going back and editing the quot…

Yes they are! Quite remarkable, really… and not noticing that they are breaking the format in the process. I guess they don’t have the preview up? Or may be doing it by mobile… And the person who did this one of the principles in the business… glad I didn’t make him an editor! :slight_smile:

Aha! Mobile is a good bet. It’s hard too select just right and then you’d be ham-handed and have no preview when you tried to “fix” it.

This is still a recurring issue in my system. Here’s a message which came up today: [image] I edited the post with a carriage return after the closing quote tag, but still find it surprising that the text stream isn’t parsed like HTML where line feeds and carriage returns don’t impact the function…

No, that’s how the tags work. You can’t randomly insert them in random order and expect things to work.

The order isn’t random, it is just fine. But unlike HTML, in this system is matters where the linefeeds happen to fall. All it took to fix that broken post was adding a line feed / CR after the closing tag. I’m willing to keep manually editing posts when users fail to comply with the required str…

Take a look at the markdown spec. Unlike HTML markdown is entirely dependent on well-placed line breaks. An errant line break in an <h1> element wouldn’t have any impact on rendering, but: here in markdo wn world it does This is true for lots of elements, markdown tables are horribly broken by ad…

[图片] Stephen: throwing tags in without respecting structure I’m fine with navigating these waters, like any coder, but our users are civilians and would think markdown has something to do with prices at Walmart. As you say, thankfully we’re not asking them to write HTML! What is gained by…

引用上下文影响引用功能

支持

Falco (Falco) 2020 年1 月 7 日 20:16 2

This was a conscious change a few years ago:

3 个赞

话题		回复	浏览量
Can we have the old Markdown for quoting paragraphs please? Feature	17	1252	2018 年8 月 22 日
BBCode [quote] tag and mixed newlines Feature	4	1353	2022 年1 月 26 日
Markdown quote requires blank line to end quote Bug markdown , markdown-it-review	7	10927	2017 年6 月 26 日
Quotes containing code block must start with newline Bug	14	3403	2020 年5 月 15 日
"Broken" quoting of/into email Feature	17	1673	2017 年7 月 18 日

引用上下文影响引用功能

相关话题